Skip to content

Commit 7f6d0b9

Browse files
Merge pull request #215425 from billmath/ric2
updating
2 parents df054f6 + b2f2117 commit 7f6d0b9

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/active-directory/hybrid/how-to-connect-fed-o365-certs.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,9 @@ Update Microsoft 365 with the new token signing certificates to be used for the
174174
> [!NOTE]
175175
> If you need to support multiple top-level domains, such as contoso.com and fabrikam.com, you must use the **SupportMultipleDomain** switch with any cmdlets. For more information, see [Support for Multiple Top Level Domains](how-to-connect-install-multiple-domains.md).
176176
>
177-
177+
> If your tenant is federated with more than one domain, the Update-MsolFederatedDomain needs to be run for all the domains, listed in the output from `Get-MsolDomain -Authentication Federated`. This will ensure that all of the federated domains are updated to the Token-Signing certificate.
178+
>You can achieve this by running:
179+
>`Get-MsolDomain -Authentication Federated | % { Update-MsolFederatedDomain -DomainName $_.Name -SupportMultipleDomain }`
178180
179181
## Repair Azure AD trust by using Azure AD Connect <a name="connectrenew"></a>
180182
If you configured your AD FS farm and Azure AD trust by using Azure AD Connect, you can use Azure AD Connect to detect if you need to take any action for your token signing certificates. If you need to renew the certificates, you can use Azure AD Connect to do so.

0 commit comments

Comments
 (0)