How-to Get a Private Support Channel for Your Unified Integration

May 1, 2026

Unified.to offers customers 3 platforms for support:

• Slack
• Discord
• Microsoft Teams

Slack

We use Slack Connect to invite our customers into private support channels that we create in our Slack account. Just reach out to your account manager, and they will create a channel for you and invite your product team.

This is our preferred method of working with your team to get them to success faster.

Discord

Our Discord server offers both public and private channels for support. The public channels are used for anyone who is just trying out Unified.to. Once you dedicate your product team's time to integrate Unified.to into your application, please let us know and we will create a private channel for you.

Microsoft Teams

For enterprise customers, Unified also offers shared private channels in Microsoft Teams. Please let us know if you cannot use Slack nor Discord (as per your IT policy), and we will be happy yo setup Teams access and a private channel.

But, you will need your IT to also setup Teams access to the Unified MS Teams account for your team, by following this guide:

This guide is for your Microsoft Entra (Azure AD) administrator. It walks through the configuration needed on your tenant so we can collaborate with you in a Microsoft Teams shared channel.

Background

Unified.to wants to invite a user from your organization into a Microsoft Teams shared channel (sometimes referred to as a "private cross-org channel"). Unlike standard Teams channels, which require external users to be added as guests in your tenant, shared channels use Microsoft Entra B2B direct connect. This lets your user access the channel from inside their own Microsoft Teams client, without switching tenants and without being added to our directory.

For B2B direct connect to work, both tenants must trust each other. We have already configured our side. This document covers the symmetric configuration required on yours.

What you'll be enabling

You're enabling B2B direct connect with a single specific external tenant — Unified.to. Nothing else changes:

• We are not added as guests in your directory.
• Your users are not added as guests in ours.
• Your existing default cross-tenant access policy is unaffected for every other organization.
• The settings can be reverted at any time by removing the entry.

Prerequisites

• A user account in your Entra tenant with one of the following roles:
  • Global Administrator, or
  • Security Administrator, or
  • Conditional Access Administrator (with Cross-tenant access settings permission)
• Your tenant must have Microsoft Entra ID (any edition — Free is sufficient for the basic configuration described here)
• A modern browser signed in to your Microsoft 365 admin account

Our tenant details

You'll need these values during the setup:

Step-by-step setup

The full process takes about five minutes.

1. Open the Microsoft Entra admin center
   Go to https://entra.microsoft.com and sign in with your admin account.
2. Navigate to Cross-tenant access settings
   In the left navigation, expand Entra ID → External Identities → Cross-tenant access settings.
   (If you don't see External Identities directly, click "Show more" or use the search bar at the top: search for "Cross-tenant access settings".)
3. Add Unified.to as an organization
4. Make sure you're on the Organizational settings tab (not "Default settings").
5. Click + Add organization.
6. In the side panel, paste either of the following into the "Tenant ID or domain name" field:
   • Tenant ID: 4b8acf48-e5c8-4484-896b-95b1b824ddda
   • Domain: unified.to
7. Microsoft will resolve the entry and display Unified.to with our tenant ID.
8. Click Add. You should see a confirmation toast: "Successfully added Unified.to tenant to organizational settings."

Unified.to now appears in the list with both Inbound access and Outbound access showing "Inherited from default". We'll override that next.

4. Configure Inbound access

This controls whether Unified.to users can access resources in your tenant via B2B direct connect (such as joining a shared channel that we host).

1. In the 'Unified.to row', click the Inbound access link ("Inherited from default").
2. In the panel that opens, click the B2B direct connect tab.
3. Select the Customize settings radio.
4. On the External users and groups sub-tab:
   • Access status: Allow access
   • Applies to: All Unified.to users and groups
5. Switch to the Applications sub-tab:
   • Access status: Allow access
   • Applies to: All applications
6. Click Save. The Save button greys out when the save completes.
7. Close the panel (X in the top-right) to return to the Organizational settings list. The Inbound access column for Unified.to should now read "Configured".

5. Configure Outbound access

This controls whether your users can access resources hosted by Unified.to (such as the shared channel we'll invite them into).

1. In the 'Unified.to row', click the Outbound access link ("Inherited from default").
2. In the panel that opens, click the B2B direct connect tab.
3. Select the Customize settings radio.
4. On the Users and groups sub-tab:
   • Access status: Allow access
   • Applies to: All your organization name users
5. Switch to the External applications sub-tab:
   • Access status: Allow access
   • Applies to: All external applications
6. Click Save.
7. Microsoft will display a consent dialog titled "Are you sure?", explaining that enabling outbound B2B direct connect lets external organizations access limited contact data about your users for the purpose of sending connection requests. Click Yes to confirm.
8. Close the panel. The Outbound access column for Unified.to should now read "Configured".

6. Verify

The Unified.to row in your Organizational settings should now show:

What about Microsoft Teams settings?

In most tenants, the Teams admin center already permits shared channel collaboration with external orgs by default. If a user from your side reports they cannot accept our shared-channel invite, your Teams admin should verify:

• Microsoft Teams admin center → Teams → External access → "Allow Teams accounts not managed by an organization" or per-domain allow list (if your org uses an allow list, add unified.to).
• Microsoft Teams admin center → Teams → Teams policies → the policy assigned to the affected user has "Create shared channels" and "Invite external users to shared channels" enabled (or at minimum, "Join external shared channels").

These Teams-level settings are usually permissive by default. The Entra cross-tenant configuration above is the part that's typically missing.

Replication delay

Cross-tenant configuration can take up to 15 minutes to propagate across Microsoft's services. If we attempt to invite your user into the shared channel right after you finish, and it fails, please ask us to wait ten minutes and retry before troubleshooting further.

Letting us know you're done

Once Inbound and Outbound both read "Configured" for Unified.to on your side, please let us know. We'll then send the shared-channel invite to the user(s) you specify, and they'll see the invitation appear in their own Microsoft Teams client.

Reverting later

To remove the trust relationship at any time:

1. Microsoft Entra admin center → External Identities → Cross-tenant access settings → Organizational settings.
2. Find the Unified.to row, click the trash icon at the right, and confirm.

This restores your default policy for our tenant. Any active shared channels become inaccessible to your users at that point.

Reference

Microsoft's official documentation:

• B2B direct connect overview: https://learn.microsoft.com/entra/external-id/b2b-direct-connect-overview
• Configure cross-tenant access settings: https://learn.microsoft.com/entra/external-id/cross-tenant-access-settings-b2b-direct-connect
• Shared channels in Microsoft Teams: https://learn.microsoft.com/microsoftteams/shared-channels