title: Amazon Alexa Account Linking doesn't work with Azure AD B2C
body: <p>For two days I try to use an Azure AD B2C with Amazon Alexa for account linking without success.
  Neither Alexa, neither ad b2c offer a way to debug and I can't see exchange between services.</p>
  
  <p>Is there anybody who have succeeded to do this ?</p>
  
  <p><strong>EDIT: Thanks to Saeed Akhter, I finally succeed in Alexa/B2C configuration.</strong></p>
  
  <p>In AD B2C :</p>
  
  <ol>
  <li>Create a app that represents my web app called by the alexa skills.
  
  <ul>
  <li>Include web api: yes</li>
  <li>Authorize implicit: yes</li>
  <li>Configure an App ID (<code>https://{tenant}/{myapi}</code>)</li>
  <li>Save</li>
  <li>Publish scope with a descriptive name and a value. The important label is the value and not the name.</li>
  <li>Save</li>
  </ul></li>
  <li>Create a second app for Alexa
  
  <ul>
  <li>Include web api: yes</li>
  <li>Authorize implicit: yes</li>
  <li>Response URL: set the two urls provided by Alexa</li>
  <li>Save</li>
  <li>Go to Api Access > Add > Select the previous API, select all and save</li>
  </ul></li>
  </ol>
  
  <p>In Alexa configuration panel :</p>
  
  <ul>
  <li>Authorization URL: take the url found in <code>https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration?p={policy}</code></li>
  <li>Client id: The application id of your Alexa app in B2C</li>
  <li>Domain List: login.microsoftonline.com</li>
  <li>Scope: 
  
  <ul>
  <li>openid</li>
  <li><code>https://{your Alexa application id you setted in B2C}/{your custom scope value}</code></li>
  </ul></li>
  <li>Access token URI: take the url found in <code>https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration?p={policy}</code></li>
  <li>Client Secret: The secret generated by B2C for your Alexa app</li>
  </ul>
  
  <p>After that, if you try the account linking from Alexa, everything should work!</p>