Microsoft small business knowledge base

Article ID: 2174324 - Last Review: December 12, 2014 - Revision: 19.0


When you make a change to a parent (top-level) domain that's verified in Office 365, Microsoft Azure, or Microsoft Intune, a child domain that's also verified 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 Active Directory Federation Services (AD FS) relying party trust
  • Verify domain ownership


To resolve this issue, delete the child domain, add and verify the parent domain, and then re-add the child domain.

Note After the parent domain is verified and the child domain is added, you don't have to verify the child domain because it inherits the settings (verification, authentication, and federation) from its parent.


This issue may occur if the child domain is verified before the parent domain is verified. When the child domain is verified first, verification and its settings are managed independently of the parent domain.

For example, you verify the domain. Later, you verify the domain. When you verify, and ownership is proven, the namespace is created in Office 365 as a domain that's completely independent of Therefore, when you later verify, any changes that are made to this new domain don't affect

In certain cases, you may want to manage the child domain properties independent of the parent domain.


Still need help? Go to the Office 365 Community ( website or the Azure Active Directory Forums ( website.

Applies to
o365 o365e o365m o365a o365022013 KB2174324
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support