This project is read-only.


The instructions on /Home/Start are inaccurate


I've tried setting up the service gateway management console site a couple of times today and always end up hitting a brick wall when I try to click the "Sign In To Continue" button at the bottom of "/Home/Start" after I attempt to follow the instructions on "/Home/Start". I get an error stating my MS account "is not supported for sign-in to this application."

I must be doing something wrong since I can't sign in at the end but it's hard to troubleshoot because the instructions don't match the current Azure AD application wizard. For example, step 6 on "/Home/Start" is a "Directory access" wizard step but if you go to Azure right now and create an Azure AD application, that step does not exist. Also, the "Web Apis" section referenced in step 7 does not exist on the Azure AD application configuration page.

Is there an updated set of instructions that corresponds to the current state of Azure?

Thank you


jamesbak wrote May 5, 2014 at 7:42 PM


Thanks for the feedback. The AAD portal experience has changed subtly underneath us and so some of the key steps in the initial configuration process are out of date. We will fix that as soon as we can.

In the interim, following are the amendments to the published instructions:
  1. Ignore Step 6 in the instructions
  2. The 'keys' section of Step 7 is still valid and required
  3. The 'web apis' portion of Step 7 should be replaced with the following. In the new 'Permissions to Other Applications' section, apply 2 configuration changes as shown in the following screen captures
Windows Azure Active Directory:

Windows Azure Service Management API:

You should then be able to enter the Client ID and Key Value values as instructed on the second page after logging in.

As always, please reach out to us if you encounter any issues, have any queries or have feedback about the product.


jamesbak wrote Jul 7, 2014 at 7:24 PM


Today, we have completed a new release of Service Gateway (v0.7). As part of the changes in this release, we have updated the documentation to reflect the current state of the Azure Management Portal.

Hope this helps!