asked on
Office 365 with SSO on subdomain
We are about to move to Office 365 and we want to sync our AD.
I have installed ADFS 2.0, DirSync etc and Everything is working fine in our test Environment.
BUT, with the real case I cant use our email domain because there is already an A record pointing to our homepage.
(And there must be an A record pointing to our local network?)
So I created a subdomain instead but when I try to federate that suddomain it only said that it isn´t supported.
Do I have to create a new domain that is unused?
Or how do I solve this?
/Peter
I have installed ADFS 2.0, DirSync etc and Everything is working fine in our test Environment.
BUT, with the real case I cant use our email domain because there is already an A record pointing to our homepage.
(And there must be an A record pointing to our local network?)
So I created a subdomain instead but when I try to federate that suddomain it only said that it isn´t supported.
Do I have to create a new domain that is unused?
Or how do I solve this?
/Peter
Microsoft 365
Last Comment
FutureITPartner
ASKER
Lets say that our email domain is: maindomain.com
And my our website is: www.maindomain.com
When we configure O365 and SSO I have to make maindomain.com point to our WAN IP so that we can forward port 443 to our ADFS server. That is, create an public A record to our WAN IP.
But we have an A revord already for maindomain.com, pointing to our ISP.
Hope you understand what I meen :-)
And my our website is: www.maindomain.com
When we configure O365 and SSO I have to make maindomain.com point to our WAN IP so that we can forward port 443 to our ADFS server. That is, create an public A record to our WAN IP.
But we have an A revord already for maindomain.com, pointing to our ISP.
Hope you understand what I meen :-)
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I tried using o365.maindomain.com but when I tried to convert it to federate, Powershell gave an error about that it wasn´t supported.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
OK. I tried it again and now its working like you said.
I have done that before and it didn´t work.
I Think it was because I first added maindomain.com to Office365 och converted it to Federated. Then I added o365.maindomain.com a couple of Days later, and changed the IIS etc.
This time I converted maindomain.com to standard then I converted it to Federated when o365.maindomain.com was present in the O365.
Could this be the case?
I have done that before and it didn´t work.
I Think it was because I first added maindomain.com to Office365 och converted it to Federated. Then I added o365.maindomain.com a couple of Days later, and changed the IIS etc.
This time I converted maindomain.com to standard then I converted it to Federated when o365.maindomain.com was present in the O365.
Could this be the case?
(And there must be an A record pointing to our local network?)" which A record are you referring to specifically?