Call Manager supports both Microsoft Commercial Cloud and Microsoft GCC High (GCCH). Once configured, Provisioner will be able to create and manage both Commercial and GCCH customer tenants from a single portal.
Add Branded GCC High Cloud Support
Reach out to your account manager if you wish to add support for GCCH to your brand. The primary step required from the brand owner is creation of additional app registrations in a suitable GCCH tenant.
Adding a GCC High Customer
In Provisioner, the process is exactly the same as Commercial tenants. When creating a customer service instance (e.g. a Call Manager instance), the platform will look-up the relevant cloud for the email address entered, and then complete the form accordingly, selecting Commercial or GCCH as required. You can also manually complete the form if required:
Once the customer service instance is created, it can be managed as normal. Clicking 'Access Service' will drop you into a Call Manager session. This works even when your logged in as a commercial cloud user in Provisioner and then click 'Access Service' for a GCCH tenant due to the delegated access part of the platform.
Browsing Direct to Call Manager - Additional Username Prompt
If your brand is enabled for both Commercial and GCCH clouds then the login process for users that go direct to the portal.us.$your-brand web address is slightly different. The very first time the user browses to the page, they will be prompted to enter their username:
Once the username field is completed, if the primary 'Sign In' button is selected then the platform will lookup the appropriate cloud required for login based on the username's domain and Microsoft's API. Alternatively, you can specifically select to login with Commercial or GCCH clouds.
This additional step is required as the platform needs to ensure it sends you to the appropriate Microsoft login page. Microsoft run completely separate login pages (login.microsoftonline.com for Commercial, login.microsoftonline.us for GCC High). The username prompt and cloud detection ensures the platform redirects the user to the correct one.
Where possible, the platform will remember the previous choice to avoid showing the Sign In page more often than required. Users navigating from Provisioner will never see this page, as the platform already knows the logged-in user cloud and the target tenant cloud.