From 26f5fa8f46054318f577d7281180228682c9994d Mon Sep 17 00:00:00 2001 From: Oren Novotny Date: Wed, 20 Dec 2017 12:58:25 -0500 Subject: [PATCH] Update deployment docs --- docs/Deployment.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/Deployment.md b/docs/Deployment.md index 612dacb..37e6e1d 100644 --- a/docs/Deployment.md +++ b/docs/Deployment.md @@ -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.