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
When I quit and then restart the add-on, in the "Sign in to Azure Automation" field, it has the UPN that I last used to login with the plugin (say, [email protected]). OTOH, my Win 10 desktop is bound to Azure AD as (say) [email protected].
When I click the "Sign In" button, the Addon seems to ignore the current field value (admin@...), and instead SSO's into Azure as user@. My user account has no admin rights in Azure, so the add-on throws the "No subscriptions found for this user account, please create one in the Azure portal" and grinds to a halt. Then, in the add-on, I click "switch user", type in "[email protected]", and after password and MFA challenge, I'm in as the user I want to connect as.
This causes a certain amount of teeth grinding, is there some way the addon can be persuaded to honour the value in the Sign In field?
Cheers
simon
The text was updated successfully, but these errors were encountered:
Less a bug, more a UX issue...
When I quit and then restart the add-on, in the "Sign in to Azure Automation" field, it has the UPN that I last used to login with the plugin (say, [email protected]). OTOH, my Win 10 desktop is bound to Azure AD as (say) [email protected].
When I click the "Sign In" button, the Addon seems to ignore the current field value (admin@...), and instead SSO's into Azure as user@. My user account has no admin rights in Azure, so the add-on throws the "No subscriptions found for this user account, please create one in the Azure portal" and grinds to a halt. Then, in the add-on, I click "switch user", type in "[email protected]", and after password and MFA challenge, I'm in as the user I want to connect as.
This causes a certain amount of teeth grinding, is there some way the addon can be persuaded to honour the value in the Sign In field?
Cheers
simon
The text was updated successfully, but these errors were encountered: