Hi guys -
I have a possible integration scenario where a company is effectively splitting their infrastructure, networks and their email systems into two, but want to retain a single SMTP address space. There aren't a large number of objects in the two organisations, so the intention is manage routing via secondary SMTP domains, and to create contacts in each platform with a unique alias, and theexternal E-mail address attribute populated with the secondary domain value. Below is an example of how a typical user "Bob" would be represented in both environments.
Company A:
- Exchange 2010
- Object type: Mailbox
- Primary SMTP address: bob@contoso.com
- Secondary alias: bob@companya.contoso.com
Company B:
- Exchange 2013
- Object type: Contact
- Primary SMTP address: bob@contoso.com
- Secondary/external alias: bob@companya.contoso.com
I'm confident the email routing will work as intended, but the intention is to also use the Microsoft Federation Gateway to exchange free/busy information between the two organisations.
Question: If a user in Company B selects an address book contact from Company A, and goes to look up their free/busy information via the MFG, will the MFG use theirprimary address, or or their secondary/external address to look up their free/busy information via Exchange Web Services?
I'm hoping it the MFG will use their secondary/external alias to look up the free/busy as these sub-domains will be registered as part of the Federation Trust config.
Regards, James
James Frost