Case Study / Outpost space

Teams calling in GCC and GCC High, on one secure path

Outpost had Teams users in two government clouds and no phone calling in either. Intuity brought compliant and secure dial tone to both.

The challenge

Outpost’s defense work runs on CUI, and its collaboration already lived in Microsoft’s government clouds. Voice did not. Its GCC tenant had no voice platform, and its GCC High tenant had no connection to the phone network. Microsoft Calling Plans are not available in GCC High, so Outpost needed a carrier that could deliver Direct Routing inside the compliant boundary and serve both tenants.

The solution

Intuity configured Direct Routing separately in each tenant and connected both to Intuity Connex. Calls travel encrypted with TLS and SRTP, are screened by AIDN, and arrive in the Teams client users already use. Intuity built the SBC routing, calling policies, dial plans and number assignments in each tenant, then validated inbound and outbound calling in both.

The result

Every active Teams user at Outpost can now place and receive outside calls, in both clouds, through one Intuity architecture and one US-based support team.
Testimonial

“Managing GCC and GCC High separately would have meant another carrier, another support contact, and more complexity. Intuity UC brought both environments under one secure architecture and kept the Teams experience seamless for our users.”

At a glance

Client
Outpost, reusable space cargo return
Environments
GCC (OutpostHQ) and GCC High
Solution
Intuity Connex Direct Routing, AIDN screening
Outcome
Native Teams calling for all active users in both tenants

Running into the same problem?

A line matched to the client’s industry sits here.

● We respond within 1 Business Day

Request Your
Custom Quote

Tell us about your setup and we will build a plan around it.

Contact Form (Leave this Default Form - it has settings configured)

We never sell your information. See our Privacy Policy.

Why organizations choose Intuity

Scroll to Top