asked on

Exchange 2013 Hybrid setup - HCW0 No federation trust is configured for this organization

Hello -

I am in the process of setting up a Hybrid Exchange Deployment for my company. Our on-prem environment:

1x 2007 Exchange Mailbox server
1x 2013 Exchange Hybrid/CAS server

After filling out all of the required fields in the Hybrid Configuration Wizard, I end up receiving an error:

Command: Set-FederatedOrganizationIdentifier -DefaultDomain '<our tenant>.mail.onmicrosoft.com' -Enabled: $true

HCW0 - Powershell failed to invoke 'Set-FederatedOrganizationIdentifier': No federation trust is configured for this organization or no domain is federated as the account namespace.

From this post (https://www.reddit.com/r/exchangeserver/comments/53vk0b/hybrid_config_error/), I tried running the following command:

Set-FederatedOrganizationIdentifier -DefaultDomain '<our tenant>.mail.onmicrosoft.com' -Enabled: $true

Open in new window

but I receive the following error:

No federation trust is configured for this organization or no domain is federated as the account namespace.
    + CategoryInfo          : InvalidOperation: (Federation:ADObjectId) [Set-FederatedOrganizationIdentifier], NoTrust
   ConfiguredException
    + FullyQualifiedErrorId : [Server=BN6PR17MB1266,RequestId=dae6cab9-4b0a-417f-ac4a-51d719f8cdde,TimeStamp=2/16/2017
    9:09:37 PM] [FailureCategory=Cmdlet-NoTrustConfiguredException] B2DC7700,Microsoft.Exchange.Management.SystemConf
  igurationTasks.SetFederatedOrganizationIdentifier
    + PSComputerName        : outlook.office365.com

Open in new window

Get-FederatedOrganizationIdentifier shows:

RunspaceId          : fa3d6b54-6622-427b-b749-5934d3238056
AccountNamespace    : <our tenant>.onmicrosoft.com
Domains             : {<domain1>.com, <our tenant>.mail.onmicrosoft.com, <domain2>.com, <our tenant>.onmicrosoft.com}
DefaultDomain       :
Enabled             : True
OrganizationContact :
DelegationTrustLink : MicrosoftOnline
Identity            : Federation
IsValid             : True
ExchangeVersion     : 0.10 (14.0.100.0)
Name                : Federation
DistinguishedName   : CN=Federation,CN=Configuration,CN=<our tenant>.onmicrosoft.com,CN=ConfigurationUnits,DC=NAMPR07A002
                      ,DC=prod,DC=outlook,DC=com
Guid                : 3f7dea84-f9d8-4b40-948a-5173f9d5e575
ObjectCategory      : NAMPR07A002.prod.outlook.com/Configuration/Schema/ms-Exch-Fed-OrgId
ObjectClass         : {top, msExchFedOrgId}
WhenChanged         : 2/10/2015 11:57:20 PM
WhenCreated         : 5/12/2014 6:51:44 PM
WhenChangedUTC      : 2/11/2015 4:57:20 AM
WhenCreatedUTC      : 5/12/2014 10:51:44 PM
OrganizationId      : NAMPR07A002.prod.outlook.com/Microsoft Exchange Hosted Organizations/<our tenant>.onmicrosoft.com
                      - NAMPR07A002.prod.outlook.com/ConfigurationUnits/<our tenant>.onmicrosoft.com/Configuration
Id                  : Federation
OriginatingServer   : BLUPR07A002DC03.NAMPR07A002.prod.outlook.com
ObjectState         : Changed

Open in new window

Any ideas on why the HCW will not finish configuring? Or where I could look next?

Thank you!

SOLUTION

Adam Brown

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Hi Adam -

Thanks for the reply! I was under the impression that a Hybrid Exchange Deployment could be completed apart from ADFS. Perhaps I'm heading in the wrong direction for the type of deployment that I'm actually wanting?

While my company may eventually opt to setup ADFS for the purpose of SSO, we are just looking to sync up our AD directory services to Azure (which has been completed) and migrate a handful of mailboxes to Exchange Online.

ASKER

I called in to 365 support, who clarified that we do indeed need an ADFS environment set up in order to complete Hybrid Deployment. The documentation I had been following was incorrect. :(

That being said, after fully deploying and testing an ADFS 3.0 environment, the Hybrid Configuration Wizard is still showing the same error. I reached out to 365 Support again, who elevated this to their back-end Exchange Team. Been waiting for an update for a little over a week now...

I'll update this question with whatever the fix turns out to be, once they provide it.

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Adam was a huge help pointing me towards ADFS to set up that piece of the puzzle. The ultimate fix ended up being the move to an entirely new tenant, as our original tenant was corrupt and Microsoft Support was unable to resolve it for us.