A sub-domain doesn't inherit the changes that are made to the top-level domain in Office 365

Article ID: 2174324 - View products that this article applies to.

Not sure what release of Office 365 you're using? Go to the following Microsoft website:
Am I using Office 365 after the service upgrade?
(http://office.microsoft.com/redir/HA103982331.aspx)
Expand all | Collapse all

PROBLEM

When you make a change to a top-level domain that's registered with Microsoft Office 365, a sub-domain that's also registered with Microsoft Office 365 doesn't inherit the changes. This issue may occur when you do one of the following:
  • Change the domain from standard to federated
  • Change the domain from federated to standard
  • Set domain authentication or federation configurations
  • Update the domain AD FS relying party trust
  • Verify domain ownership
Back to the top | Give Feedback

SOLUTION

To resolve this issue, delete the sub-domain by using the Office 365 portal or Windows Azure Active Directory Module for Windows PowerShell, create and verify the parent domain, and then re-create the sub domain.

Note After the parent domain is verified and the sub-domain is added, you don't have to verify the sub-domain because it will inherit settings (verification, authentication, and federation) from its parent.
Back to the top | Give Feedback

MORE INFORMATION

This issue may occur if the sub-domain is registered with Microsoft Office 365 before the top-level domain is registered with Microsoft Office 365. When the sub-domain is registered first, its Microsoft Office 365 verification and settings are managed independently of the parent domain.

For example, consider the following scenario. You register the domain corp.constoso.com. Later, you register the domain contoso.com. In this scenario, when you register corp.contoso.com and ownership is proven, the namespace is created in Microsoft Office 365 as a domain that's completely independent of contoso.com. Therefore, when you later register contoso.com, changes to this new domain don't affect corp.contoso.com.

In certain scenarios, you may want to manage domain properties of an Office 365 sub-domain independent of its parent domain. To deliberately achieve the opposite of the resolution in this article, the sub-domain must be created in Office 365 before the parent domain is created. You can't break the inheritance relationship between an existing Office 365 parent domain and all inheriting sub-domains unless you first delete the parent domain from Office 365.
Back to the top | Give Feedback

Still need help? Go to the Office 365 Community
(http://community.office365.com/)
website.
Back to the top | Give Feedback

Properties

Article ID: 2174324 - Last Review: May 15, 2013 - Revision: 10.0
Applies to
  • Microsoft Office 365 for enterprises (pre-upgrade)
  • Microsoft Office 365 for education  (pre-upgrade)
  • Microsoft Office 365
Keywords: 
o365 o365e o365m o365a o365062011 pre-upgrade o365022013 after upgrade KB2174324
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top