Merge pull request #188135 from RobdeJong/patch-131

Update plan-connect-topologies.md

Author: PRMerger-2

articles/active-directory/hybrid/plan-connect-topologies.md

@@ -151,13 +151,11 @@ This topology implements the following use cases:
 *	It is supported to have different sync scopes and different sync rules for different tenants.
 *	Only one Azure AD tenant sync can be configured to write back to Active Directory for the same object. This includes device and group writeback as well as Hybrid Exchange configurations – these features can only be configured in one tenant. The only exception here is Password Writeback – see below.
 *	It is supported to configure Password Hash Sync from Active Directory to multiple Azure AD tenants for the same user object. If Password Hash Sync is enabled for a tenant, then Password Writeback may be enabled as well, and this can be done on multiple tenants: if the password is changed on one tenant, then password writeback will update it in Active Directory, and Password Hash Sync will update the password in the other tenants.
-*	It is not supported to add and verify the same custom domain name in more than one Azure AD tenant, with one exception: it is supported to [add and verify](../fundamentals/add-custom-domain.md) a custom domain name in a tenant in the Azure Commercial environment and subsequently add and verify that same domain name in a tenant in the Azure Government environment. Note that the custom domain name **MUST** exist in Commercial Azure AD tenant before it can be verified in the Azure Government Azure AD tenant.
+*	It is not supported to add and verify the same custom domain name in more than one Azure AD tenant, even if these tenants are in different Azure environments.
 *	It is not supported to configure hybrid experiences such as Seamless SSO and Hybrid Azure AD Join on more than one tenant. Doing so would overwrite the configuration of the other tenant and would make it unusable. 
 *	You can synchronize device objects to more than one tenant but only one tenant can be configured to trust a device.
 * Each Azure AD Connect instance should be running on a domain-joined machine.
 
-Related information : [Federate multiple instances of Azure AD with single instance of AD FS](./how-to-connect-fed-single-adfs-multitenant-federation.md)
-
 >[!NOTE]
 >Global Address List Synchronization (GalSync) is not done automatically in this topology and requires an additional custom MIM implementation to ensure each tenant has a complete Global Address List (GAL) in Exchange Online and Skype for Business Online.