Customers configuring the SSO with our EntraID connector should be encouraged to enter their EntityID within the console as either https://someDomain.com or urn:uri:someDomain.com. The New-MgDomainFederationConfiguration will always throw an error that the issuerUri (EntityID) domain is incorrect without either prepending the domain with https:// or urn:uri:
The PowerShell Module will be updated along with documentation to state this requirement. If an EntityID value does not contain this prefix, the PowerShell Module will now throw an error:
The domain names should be extracted and passed into New-MgDomainFederationConfiguration to correctly identify the domain to be modified.
Issues
What does this solve?
Customers configuring the SSO with our EntraID connector should be encouraged to enter their EntityID within the console as either
https://someDomain.comorurn:uri:someDomain.com. TheNew-MgDomainFederationConfigurationwill always throw an error that the issuerUri (EntityID) domain is incorrect without either prepending the domain withhttps://orurn:uri:The PowerShell Module will be updated along with documentation to state this requirement. If an EntityID value does not contain this prefix, the PowerShell Module will now throw an error:
The domain names should be extracted and passed into
New-MgDomainFederationConfigurationto correctly identify the domain to be modified.Is there anything particularly tricky?
How should this be tested?
Screenshots