botframework-sdk: Getting Refresh access token failed with status code: 400

Yes! Working again!

@bilby91 Have you restarted the service?

@All There was an issue with Azure AAD last night that affected bots. It has been resolved. If your bots are still experiencing issues, please restart the service.

All of our bots seem stable again and got a call from MS saying it should be working again. Our support ticket hasn’t been closed yet though, but will post back here again once it is officially resolved.

Not Yet working on all environments ,All directline based bots are not up yet.

Same here. We have started to receive this error in all of our environments (Development, Staging and Production):

SDK Platform: NodeJS SDK Version 3.x Active Channel: Messenger, Skype, MS Teams, Slack, WebChat Deployment Environment : Azure Bot service (Web App)

Error:

Error: Refresh access token failed with status code: 400
at new Error (native)
at Error.AppInsightsAsyncCorrelatedErrorWrapper (D:\home\site\wwwroot\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:173:18) [<root>]
at Request._callback (D:\home\site\wwwroot\node_modules\botbuilder\lib\bots\ChatConnector.js:561:28) [<root>]
at Request.self.callback (D:\home\site\wwwroot\node_modules\request\request.js:186:22) [<root>]
at Zone.runTask (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:151:47) [<root> => <root>]
at Request.ZoneTask.invoke (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:345:33) [<root>]
at emitTwo (events.js:106:13) [<root>]
at Request.emit (events.js:191:7) [<root>]
at Request.<anonymous> (D:\home\site\wwwroot\node_modules\request\request.js:1163:10) [<root>]
at Zone.runTask (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:151:47) [<root> => <root>]
at Request.ZoneTask.invoke (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:345:33) [<root>]
at emitOne (events.js:96:13) [<root>]
at Request.emit (events.js:188:7) [<root>]
at IncomingMessage.<anonymous> (D:\home\site\wwwroot\node_modules\request\request.js:1085:12) [<root>]
at IncomingMessage.g (events.js:292:16) [<root>]
at Zone.runTask (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:151:47) [<root> => <root>]
at IncomingMessage.ZoneTask.invoke (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:345:33) [<root>]
at emitNone (events.js:91:20) [<root>]
at IncomingMessage.emit (events.js:185:7) [<root>]
at endReadableNT (_stream_readable.js:974:12) [<root>]
at Zone.runTask (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:151:47) [<root> => <root>]
at ZoneTask.invoke (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:345:33) [<root>]
at args.(anonymous function) (D:\home\site\wwwroot\node_modules\zone.js\dist\zone-node.js:1497:25) [<root>]

Seems to be a server issue: when I try to create a new Bot Channels Registration in Azure it fails with the following message:

One or more objects referenced by the access token were not found. Request ID: 95c85886-994a-435d-873e-90d8774f56e6, Timestamp: 04/06/2018 10:00:27

Please check that your account has sufficient access to the Microsoft App Registration Portal link below.

Open App Registration Portal Alternatively, use the “Create New” option in “Microsoft App ID and password” sub section to create a Microsoft App ID and password manually.

The App Registration Portal seems to have an issue as well: https://apps.dev.microsoft.com/portal/register-app