PowerShell connection issues to EOP after Tenant Relocation in Office 365 Dedicated/ITAR (vNext)

Symptoms
In Microsoft Office 365 Dedicated/ITAR (vNext), you experience Remote PowerShell connectivity issues to Microsoft Exchange Online Protection (EOP) after you perform a Tenant Relocation operation.
Cause
During the transition to vNext, the current EOP tenants will be migrated into your newly created vNext tenants. This means that all the transport rules, configurations, and user accounts will be migrated over in preparation for your move to vNext.
Resolution
As soon as you have completed the Tenant Relocation process, you should use the temporary custom vanity domain name for Remote PowerShell Connections instead of the standard URL.

After you complete your transition from ANSI to vNext, your Temporary URL will be transferred back to your primary site, and all connections will flow through there again.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 3158800 - Last Review: 04/26/2016 16:45:00 - Revision: 1.0

Microsoft Business Productivity Online Dedicated, Microsoft Business Productivity Online Suite Federal

  • vkbportal226 KB3158800
Feedback