Commands › Exchange Online
Add-FederatedDomain
Configure a secondary domain with the federated organization identifier in the federation trust for the Exchange organization. The domains being added to the federation trust must exist as accepted domains in the Exchange organization.
Quick start script
# Add-FederatedDomain — quick start (serv365.ai)
# 1. Connect (app-only shown; interactive: omit the certificate parameters)
Connect-ExchangeOnline -CertificateThumbprint $thumb -AppId $appId -Organization $org
# 2. Run and inspect
Add-FederatedDomain -DomainName <SmtpDomain> | Format-List
# 3. Export for evidence / drift tracking
Add-FederatedDomain | Export-Clixml .\FederatedDomain-$(Get-Date -Format yyyyMMdd).xmlSyntax
Add-FederatedDomain [[-Identity] <OrganizationIdParameter>] -DomainName <SmtpDomain>
[-Confirm]
[-DomainController <Fqdn>]
[-WhatIf]
[<CommonParameters>]Parameters (5)
| Parameter | Type | Required | What it controls |
|---|---|---|---|
| -Identity | OrganizationIdParameter | This parameter is reserved for internal Microsoft use. | |
| -DomainName | SmtpDomain | yes | The DomainName parameter specifies the secondary domain to be configured. |
| -Confirm | SwitchParameter | The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. | |
| -DomainController | Fqdn | The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name... | |
| -WhatIf | SwitchParameter | The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. |
Reference facts derived from Microsoft documentation, © Microsoft, licensed CC BY 4.0; restructured with original guidance by serv365.ai.