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

[BUG] Your sign-in was successful but your admin requires the device requesting access to be managed by Microsoft Non-Production to access this resource. #490

Open
ekgershg opened this issue Oct 2, 2024 · 2 comments
Labels
bug Something isn't working Priority 2

Comments

@ekgershg
Copy link

ekgershg commented Oct 2, 2024

To Reproduce

Commands you ran

az login --tenant XXXXX

Observed Behavior

Help us keep your device secure
Your sign-in was successful but your admin requires the device requesting access to be managed by Microsoft Non-Production to access this resource.


Troubleshooting details
If you contact your administrator, send this info to them.

Error Code: 530033
Request Id: b20babdf-e2a4-4fb2-a270-2b0f5b3b4a00
Correlation Id: 
Timestamp: 2024-10-02T10:35:27.070Z
App name: Microsoft Azure CLI
App id: 
IP address: 
Device identifier: 
Device platform: Windows 10
Device state: Compliant
Flag sign-in errors for review: [Enable flagging](https://login.microsoftonline.com/common/debugmode)
If you plan on getting help for this problem, enable flagging and try to reproduce the error within 20 minutes. Flagged events make diagnostics available and are raised to admin attention.

Expected behavior

A clear description of what you expected to happen instead.

Login from Azure Portal CLI into Microsoft Non-Production subscription. Or executing "az login" will automatically connect to my default tenant/subscription.

Is this specific to Cloud Shell?

Please verify if the same issue can be reproduced by running the same tool outside Cloud Shell - for example,
by installing it on your own computer. If so, it is likely to be a bug in that tool or in the Azure service it communicates with,
not in Cloud Shell. Please file the issue with the appropriate project.

Local execution of "az login" doesn't have this issue.

Interface information

How are you accessing Cloud Shell - https://shell.azure.com, https://portal.azure.com, via Windows Terminal, or some other method?
If a browser, which Operating System and browser are you using? (ex. Edge on Windows 10)

https://portal.azure.com
Windows 10

Additional context

Add any other context about the problem here.

@ekgershg ekgershg added bug Something isn't working Triage-needed Triage needed by Cloud Shell team labels Oct 2, 2024
@mbifeld
Copy link
Member

mbifeld commented Oct 8, 2024

Hi @ekgershg, thank you for reporting the issue. Is this an internal tenant login you are logging into? Can you share screenshots please? If you are an internal employee and this is sensitive information, feel free to reach out to me directly.

@mbifeld mbifeld added Priority 2 and removed Triage-needed Triage needed by Cloud Shell team labels Oct 8, 2024
@ekgershg
Copy link
Author

ekgershg commented Oct 8, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority 2
Projects
None yet
Development

No branches or pull requests

2 participants