You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To enhance the security, Azure PowerShell are going to disable the users from other organizations or Microsoft account (consumers) to sign in with Azure PowerShell to the tenants where they aren't invited as guests.
If you would like to sign in to a tenant which they are not invited as the guest
You will see following error message in the web browser:
Selected user account does not exist in tenant '$YourTenantName' and cannot access the application '1950a258-227b-4e31-a9cf-717495945fc2(Microsoft Azure PowerShell) ' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.
In order to log in a tenant, make sure the user is either
a member of that tenant
a guest invited to that tenant
Check whether you are the member of the tenant
Suppose your account name is "[email protected]" and tenant Id is "$tenantId"
Please run
When you get the list of the tenants, please check whether "$tenantId" is in it. If not or even the list is empty, you should ask the tenant admin to invite you.
Invite a guest member
If you are a tenant member, you are able to invite a guest member to your tenant. The guest user will receive an email invitation to join the tenant. Once they accept the invitation, they will be added as a guest user and can access the tenant's resources.
Note
The change will affect all the Azure PowerShell versions
We are going to release the change earlier in 2025. Please leave a comment if your use case are blocked by the changes and we will provide the proposal to unblock it.
The text was updated successfully, but these errors were encountered:
msJinLei
added
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
labels
Dec 17, 2024
msJinLei
changed the title
Tenanted passthrough Is Going to be Disabled for Azure PowerShell
Tenanted Passthrough Is Going to be Disabled for Azure PowerShell
Dec 17, 2024
msJinLei
removed
the
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
label
Dec 17, 2024
Annoucement
To enhance the security, Azure PowerShell are going to disable the users from other organizations or Microsoft account (consumers) to sign in with Azure PowerShell to the tenants where they aren't invited as guests.
If you would like to sign in to a tenant which they are not invited as the guest
You will see following error message in the web browser:
In order to log in a tenant, make sure the user is either
Check whether you are the member of the tenant
Suppose your account name is "[email protected]" and tenant Id is "$tenantId"
Please run
When you get the list of the tenants, please check whether "$tenantId" is in it. If not or even the list is empty, you should ask the tenant admin to invite you.
Invite a guest member
If you are a tenant member, you are able to invite a guest member to your tenant. The guest user will receive an email invitation to join the tenant. Once they accept the invitation, they will be added as a guest user and can access the tenant's resources.
Note
The change will affect all the Azure PowerShell versions
We are going to release the change earlier in 2025. Please leave a comment if your use case are blocked by the changes and we will provide the proposal to unblock it.
The text was updated successfully, but these errors were encountered: