We're using an ADFS server with an additional WAP server for an on-premise deployment of CRM 2013. We're in the process of implementing Windows Intune and would like to leverage our existing servers. When going through the steps to set up a trust between
AD FS and Azure AD (http://technet.microsoft.com/en-us/library/jj205461.aspx) we ran: New-MsolFederatedDomain –DomainName but received:
New-MsolFederatedDomain : The domain already exists as a standard authentication domain. To convert the domain to identity federation, use convert-MSOLDomainToFederated.
My questions is will using Convert-MsolDomainToFederated –DomainName <domain> in any way affect our existing on-premise deployment of CRM (I'm not sure what exactly it does)? Is there anything we need to consider so that it does not?
New-MsolFederatedDomain : The domain already exists as a standard authentication domain. To convert the domain to identity federation, use convert-MSOLDomainToFederated.
My questions is will using Convert-MsolDomainToFederated –DomainName <domain> in any way affect our existing on-premise deployment of CRM (I'm not sure what exactly it does)? Is there anything we need to consider so that it does not?