Sign-in & Login Problems

How to Use SupportMultipleDomain with Office 365 AD FS SSO

Kushani NimanthikaKushani Nimanthika Nov 3, 2026 869 views

Question details

The user needs to understand when and how to use the SupportMultipleDomain switch in Office 365 AD FS SSO configurations, and how to properly convert a domain back to standard authentication.

How to Use SupportMultipleDomain with Office 365 AD FS SSO
Product
Office 365
Device & OS
not provided
Scenario
Configuring single sign-on with multiple top-level domains through AD FS without deploying separate federation services.
Observed behavior
Federating separate top-level domains requires the SupportMultipleDomain switch to share AD FS handling, while converting back to standard authentication requires managing temporary user passwords.
Before you start

Ensure you have global administrator privileges in your Office 365 tenant and administrative access to the AD FS server environment before modifying domain federation settings.

Solution 1Recommended

Use the SupportMultipleDomain Switch for Top-Level Domains

Apply this switch when federating separate top-level domains to allow a single AD FS federation service to support multiple UPN suffixes.

The SupportMultipleDomain switch is crucial when dealing with multiple top-level domains (for example, newupn.com and oldupn.com) that are not subdomains of a primary company domain.

Using this switch prevents the unnecessary overhead of deploying a separate AD FS federation service instance for each UPN suffix.

1
Identify domain requirements

Verify that the domains you are federating are indeed separate top-level domains that require shared AD FS handling.

2
Execute the federation cmdlet

Open PowerShell with administrator rights and append the -SupportMultipleDomain parameter when running your federation cmdlets, such as Convert-MsolDomainToFederated or New-MsolFederatedDomain.

Use the SupportMultipleDomain Switch for Top-Level Domains
Efficient Architecture: Using this switch successfully consolidates your single sign-on architecture, reducing server overhead and management complexity.
Free Microsoft Office alternative

Simplify Your Document Workflow with WPS Office

While AD FS and SSO configurations require complex IT management in Microsoft 365 environments, your everyday document tasks shouldn't be complicated. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, ensuring smooth document creation without the enterprise administration overhead.

  1. 1. Download the installer: Visit the official WPS Office website and download the free installation package.
  2. 2. Install the suite: Run the installer and follow the on-screen prompts to set up WPS Office on your device.
  3. 3. Open your files: Launch WPS Office and directly open your existing Microsoft Word, Excel, or PowerPoint documents without losing any formatting.
Seamless compatibility with Microsoft Office file formats like DOCX, XLSX, and PPTX.Lightweight architecture that loads instantly and consumes minimal system resources.Familiar tabbed user interface, ensuring zero learning curve for traditional Office users.Completely free to download and use for your daily document management needs.
microsoft office alternative - wps office

Frequently Asked Questions

When is the SupportMultipleDomain switch absolutely required?

It is required when you are managing multiple, separate top-level domains (e.g., domainA.com and domainB.com) that need to share a single AD FS federation service instance.

What happens to user passwords when running Convert-MsolDomainToStandard?

All converted users are disconnected from SSO and assigned a randomly generated temporary password. The administrator receives a local file containing these passwords and must distribute them manually.

Can I use SupportMultipleDomain for subdomains?

If the domains are subdomains of the same parent domain, the SupportMultipleDomain switch is generally not required, as the parent domain's federation settings usually cover the subdomains automatically.

Does converting a domain to standard authentication cause downtime?

Yes, users will experience a disruption. They will be unable to log in until they receive their newly generated temporary passwords from the administrator, so the transition should be scheduled outside of peak business hours.