Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We're doing things backwards, we have an established o365 domain, with 400+ users, and are just now deploying local AD, and ADFS for SSO.

Last night, after configuring my servers, I ran the powershell command convert-MSOLdomaintofederated to convert the xxx.com vanity domain to federated, it errored out with an unspecified error(Microsoft ADFS support said the error has to do with the default password settings being changed.) And when I run convert-MSOLdomaintostandard, it comes back with the domain is already standard. Also in the o365 portal it shows the domain as standard, however it is trying to process login attempts as if it were a federated domain.

I've spent 5 hours total on the phone with Microsoft, and it has been escalated to their engineering department for resolution, sometime within the next few days... I need it yesterday.

From what we can gather, the conversion process started, error out, changed some of the internal configurations to federated, but left the description as standard.(if that makes since). So its in a weird limbo, where its in both modes but neither at the same time.

Currently, the only way to fix it is to remove the vanity domain, and re-add it.

I need a way to dissociate the user accounts from xxx.com domain to allow its removal. Removal of all the users themselves is not an option.

share|improve this question
    
hopefully theres a powershell guru who knows how to do this. –  Matt Bear Oct 30 '12 at 22:40
add comment

2 Answers 2

up vote 0 down vote accepted

This issue was resolved by microsoft, it was a replication problem between two databases on thier end.

Federation is now working correctly, and SSO works as planned.

There was no way to fix it from my end.

share|improve this answer
add comment

Please raise a case with MS support. I work in the escalations team that handle these SSO issues and we need to know the vanity domain to check a few things on the backend.

I dont believe we need to remove/add the domain again as thats drastic and very rarely needed IMHO.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.