PrepAway - Latest Free Exam Questions & Answers

You need to ensure that the federated sharing can be implemented between the organizations

You have an Exchange Server 2013 organization named contoso.com. A partner company has an
Exchange Server 2010 Service Pack 2 (SP2) organization named fabrikam.com. Both organizations
have a federated trust.
In contoso.com, you run Get-FederationInformation –DomainName contoso.com and you discover
that the TokenIssueURIs property has a value of <uri:federation:MicrosoftOnline>.
In fabrikam.com, you run Get-FederationInformation –DomainName fabrikam.com and you discover
that the TokenIssueURIs property has a value of <uri:WindowsLiveID>.
You need to ensure that the federated sharing can be implemented between the organizations.
What should you do?

PrepAway - Latest Free Exam Questions & Answers

A.
In contoso.com, install the Exchange Web Service (EWS) Managed API.

B.
In the contoso.com, run the Set-OrganizationConfig cmdlet.

C.
In fabrikam.com, run the New-FedereationTrust cmdlet.

D.
In contoso.com, run the New-FederationTrust cmdlet.

5 Comments on “You need to ensure that the federated sharing can be implemented between the organizations

  1. Billy says:

    C. Fabrikam is using a consumer instance of Azure AD, so you have to use the new federation trust wizard

    With federated sharing in Exchange Server 2013, users can share information with recipients in external federated organizations. This includes sharing their free/busy (also known as calendar availability) information for scheduling purposes or, depending on the nature of the business relationship, sharing more detailed calendar information.

    Step 1: Create and configure a federation trust
    Step 2: Create an organization relationship
    Step 3: Create a sharing policy
    Step 4: Configure an Autodiscover public DNS record

    When you create a federation trust with the Azure AD authentication system for your Exchange 2013 organization, the federation trust will use the business instance of the Azure AD authentication system. However, other federated Exchange organizations with previous versions of Exchange and existing federation trusts may be using either the business or consumer instance of the Azure AD authentication system.

    Get-FederationInformation -DomainName
    The business instance returns a value of for the TokenIssuerURIs parameter.
    The consumer instance returns a value of for the TokenIssuerURIs parameter.

    The following Exchange organizations use the business instance of the Azure AD authentication system by default:
    Exchange 2013 organizations by using the Enable federation trust wizard and self-signed certificates for a federation trust.
    Exchange 2010 SP1 or later organizations by using the New Federation Trust wizard and self-signed certificates for a federation trust.
    Exchange organizations hosted by Office 365, such as the Exchange Online.

    https://technet.microsoft.com/en-us/library/jj657483%28v=exchg.150%29.aspx




    0



    0
  2. Sanan says:

    When you create a federation trust with the Azure AD authentication system for your Exchange 2013 organization, the federation trust will use the business instance of the Azure AD authentication system. However, other federated Exchange organizations with previous versions of Exchange and existing federation trusts may be using either the business or consumer instance of the Azure AD authentication system.

    The business instance returns a value of for the TokenIssuerURIs parameter.
    The consumer instance returns a value of for the TokenIssuerURIs parameter.

    Use the New Federation Trust wizard to remove and re-create the existing federated domains and federation trusts.

    https://technet.microsoft.com/en-us/library/jj657462(v=exchg.150).aspx




    0



    0
    1. Sanan says:

      The business instance returns a value of uri:federation:MicrosoftOnline for the TokenIssuerURIs parameter.
      The consumer instance returns a value of uri:WindowsLiveID for the TokenIssuerURIs parameter.




      0



      0

Leave a Reply