Azure Bot automatic App Registration not syncing with Bot Framework directory - Error 700016

Hi ,

Thanks for reaching out to Microsoft Q&A.

This is a known issue with Azure Bot Service when using automatic app registration, especially in certain regions (East US is one of them). The error AADSTS700016 means that the App ID created during "automatic" registration is not propagating correctly into the Bot Framework tenant directory that the channel service uses. That explains why your bot can receive messages (the incoming webhook does not require token validation), but cannot respond (outbound requires token exchange against AAD and Bot Framework, which fails because the app is missing).

Here is what you need to do:

Root Cause

• When you select "Create new Microsoft App ID" during azure bot creation, the portal automatically provisions an App Registration in your tenant.
• In some cases, that app registration is not properly synced to the Bot Framework service directory (a separate multitenant directory used by Bot Service).
• As a result, outbound calls from your bot to the channel service fail with AADSTS700016: Application not found.

Workaround:

1. Manually create an App Registration in AAD:
   • Go to Azure Active Directory > App registrations > New registration.
   • Give it a name (ex: bot-teams-us-prod-manual).
   • Supported account types: Single tenant (or Multitenant if you plan crosstenant usage).
   • Redirect URI: leave blank (not needed for bots).
   • Register the app.
2. Generate a client secret:
   • In the App Reg, go to Certificates & Secrets > New client secret.
   • Copy the secret value.
3. Update the Bot Channel Registration:
   • Go to your Azure Bot resource (bot-teams-us-prod).
   • Under Configuration > Microsoft App ID and password, replace the auto gen App ID with your manually created App ID.
   • Paste the client secret.
4. Update your local bot code:
   • In .env, update & restart the bot

     MicrosoftAppId=<your-manual-app-id> MicrosoftAppPassword=<your-client-secret>

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Hello oblin denis,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Azure Bot error means that the bot's App Registration is not properly recognized by the Bot Framework directory. Try to do the followings:

1. Verify App Registration and confirm the App ID matches the one in your .env file, and make sure the app is listed and not deleted or expired.
2. Set Correct Tenant Authority in your bot’s .env file or adapter config, set:

       MICROSOFT_APP_TYPE=SingleTenant
        MICROSOFT_APP_ID=<Your App ID>
        MICROSOFT_APP_PASSWORD=<Your Secret>
        MICROSOFT_APP_TENANT_ID=<Your Tenant ID>
        MICROSOFT_APP_CHANNEL_SERVICE=https://smba.trafficmanager.net/amer/
   

   • In code (Node.js):

      const credentials = new MicrosoftAppCredentials(appId, appPassword, tenantId);
        adapter.credentials = credentials;
   

   This ensures the bot authenticates against your tenant.
3. Check Redirect URIs to ensure the following URI is present: https://token.botframework.com/.auth/web/redirect This is required for Bot Framework authentication.
4. Review API Permissions by adding:
   • Bot Framework delegated permissions
   • Microsoft Graph if needed and "Grant admin consent"
5. Recreate Bot Registration (if needed) and especially, if the app still isn’t recognized:
   • Delete the Azure Bot resource and App Registration.
   • Recreate manually via Bot Framework Developer Portal.
   • Link the new App ID and secret in Azure Bot resource - https://stackoverflow.com/questions/71031057/microsoft-bot-framework-bot-missing-from-bot-framework-tenant-how-to-add
6. Use Bot Framework Emulator with App ID and password to test token acquisition and ngrok, and Web Chat to confirm outbound messages work.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

I recreated the app id and it worked for a day. Then it stopped working again.