This commit is contained in:
Oren Novotny 2017-12-20 12:58:25 -05:00
Родитель 368018e375
Коммит 26f5fa8f46
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: D501F3955648A88A
1 изменённых файлов: 0 добавлений и 3 удалений

Просмотреть файл

@ -60,14 +60,11 @@ Azure Web Sites is the easiest way to host this service. A `B1` or higher instan
3. On the website [extensions](https://azure.microsoft.com/en-us/blog/azure-web-sites-extensions/), Add/ensure both "Application Insights" and the ".NET Core" extensions are present. Add them if required.
4. Create a new Azure Key Vault (standard is fine since it's just holding secrets). Add an access policy for your managed service identity granting it `Get` and `List` permissions for secrets.
5. Add the following secrets (you may omit ones that match the defaults in the `appsettings.json`, like `AzureAd--AADInstance` for most people). The ones are most likely:
- `Admin--Location`
- `Admin--ResourceGroup`
- `Admin--SubscriptionId`
- `AzureAd--ApplicationObjectId`
- `AzureAd--Audience`
- `AzureAd--ClientId`
- `AzureAd--ClientSecret`
- `AzureAd--Domain`
- `AzureAd--TenantId`
6. In your website [configuration](https://docs.microsoft.com/en-us/azure/app-service/web-sites-configure), add the URL to the Key Vault as a configuration option `ConfigurationKeyVaultUrl`. That's where the app will pull its configuration from.