-
Notifications
You must be signed in to change notification settings - Fork 2
Deployment Guide
The WhereOnEarthBot is mostly set up using an ARM template to create the assets but before that you need to set up a few IDs. The steps are:
- Create an App Registration
- Create a Bing Maps API Key
- Create a Google Places API Key
- Create a Resource Group
- Deploy the template
For details on what is created, take a look at the Architecture page.
The first step is to create App Registration in Azure Active Directory and then record the App ID and Secret, making sure that you select "Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" for the Supported Account Types:
To get a Bing Maps Key, follow the instructions here and then keep hold of the key for a later step.
- Click on Get Started at https://developers.google.com/places/web-service/intro (you will need to sign in with a Google account)
- Select the Places API
- Add a project name and agree to the terms of service
- Sign up to a free account - you will have to enter a debit or credit card but no charges will be made unless account upgraded to full account
- Keep the API key for later steps.
In Azure, create an empty Resource Group to use.
You can deploy the template using ARM in Visual Studio or with the button below:
Note that you may have to redeploy after the first one due to the App Service needing to exist for the Key Vault permissions to be set. Currently it can try and create the permissions before the App Service but works after a redeploy.