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

How to leave the domain after experimenting? #86

Open
glachance opened this issue Jun 25, 2018 · 1 comment
Open

How to leave the domain after experimenting? #86

glachance opened this issue Jun 25, 2018 · 1 comment
Assignees
Labels

Comments

@glachance
Copy link

glachance commented Jun 25, 2018

For the past year (2 years?) I have been stuck with an extra domain on my account. The domain was created when I used the TryAppService service.

Obviously, I don't a subscription on that domain, that was the whole point.

However, the fact that I don't have a subscription in that domain also breaks most azurerm/azuread/azurecli/msoonline powershell functions and thus making leaving the tryout domain all but impossible (?).

The online tools, like the Access Panel can't help either. I get bounced from authorize to account.activedirectory.windowsazure.com back to login.microsoftonline.com again for that domain. Either the fact that I dont have a subscription or something else about that domain trips up the site.

Aside from my own personal case, would it be possible to make absolutely certain sure that the service remove the users from the tryout domain before the end of the experiment?

(back to me again - and other users stuck with this annoyance) Is there a way for the users to forcibly leave the tryout domain when they are done / when the experimentation time has elapsed?

image

@fashaikh
Copy link

Sorry you are facing this issue.
Are you still on this tenant ? All users should have been removed. We have had reports of some users still being cached and in those cases we work with the Azure AD team to investigate and have the users removed.

@fashaikh fashaikh self-assigned this Mar 19, 2019
@fashaikh fashaikh added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants