Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bot Emulator not trusted by Microsoft #2346

Closed
mattsmall1972 opened this issue Nov 30, 2021 · 4 comments
Closed

Bot Emulator not trusted by Microsoft #2346

mattsmall1972 opened this issue Nov 30, 2021 · 4 comments
Assignees
Labels
Bot Services equired for internal Azure reporting. Do not delete. Do not change color. Bug Your classic code defect customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.

Comments

@mattsmall1972
Copy link

Version

4.14.1

Describe the bug

I am developing a Microsoft-internal bot using the Microsoft tenant with authentication. When signing in using the Emulator, a message appears that says:

You can't get there from here
This application contains sensitive information and can only be accessed from:
Devices or client applications that meet Microsoft management compliance policy.
The current browser is not supported, please use Microsoft Edge, Internet Explorer or Chrome to access this application.

To Reproduce

Steps to reproduce the behavior:

  1. Create bot in internal Microsoft tenant
  2. Set up BotAuthenticationMSGraph sample
  3. Log into the bot
  4. See error

Expected behavior

Bot is trusted by the Microsoft IT department and is usable for log in.

Screenshots

image

[bug]

@mattsmall1972 mattsmall1972 added the Bug Your classic code defect label Nov 30, 2021
@axelsrz
Copy link
Member

axelsrz commented Dec 1, 2021

Hello @tonyanziano, could you take a look at this?

@axelsrz axelsrz added Bot Services equired for internal Azure reporting. Do not delete. Do not change color. customer-reported Required for internal Azure reporting. Do not delete. labels Dec 1, 2021
@tonyanziano
Copy link
Contributor

tonyanziano commented Dec 1, 2021

This is a dupe of #2253 and you can find the explanation for the error here.

In short, sign-in was broken via a company-wide policy change and fixing it requires the implementation of an internal authentication library that the Emulator currently does not have the dev funding for.

@tonyanziano tonyanziano added the customer-replied-to Required for internal reporting. Do not delete. label Dec 1, 2021
@mattsmall1972
Copy link
Author

Thanks Tony. I'd seen that but didn't scroll down far enough to realize that it was the same one.

@sambathrajv
Copy link

This issue still exists. For those who are facing this problem, debug your bot using the steps https://learn.microsoft.com/en-us/azure/bot-service/bot-service-debug-channel-ngrok?view=azure-bot-service-4.0. Sign in steps can be verified in this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services equired for internal Azure reporting. Do not delete. Do not change color. Bug Your classic code defect customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.
Projects
None yet
Development

No branches or pull requests

4 participants