Manage Mirta PBX tenants

A PBX tenant is a customer telephony environment in Mirta PBX. MSPControl stores the tenant link, organization association and user-to-extension links while reading current tenant and extension data from Mirta.

Open Voice > PBX Tenants in the customer’s hosting space. If the menu is unavailable, first configure hosted voice with Mirta PBX.

Review the tenant list

The tenant list shows:

Column	Meaning
Tenant code	The Mirta PBX tenant identifier. It is set during creation and is read-only afterward.
Tenant name	The editable display name.
Organization	The linked MSPControl hosted organization, when configured.
Status	Whether the tenant is active or disabled in Mirta PBX.
Teams integration	Whether an Entra application registration is linked to the PBX tenant.

Create a tenant

1. Open Voice > PBX Tenants and select Add.
2. Enter a unique Tenant code and a readable Tenant name.
3. Set the extension range.
4. Configure the required tenant limits. A value of -1 represents unlimited in the current data model.
5. Optionally set the alert email, note and expiration date.
6. Optionally select an available hosted organization.
7. Save the tenant.
8. Return to the tenant list and confirm that the tenant is present with the expected organization and status.

Tenant code and extension range start are create-time values

The current provider model sends Tenant code and Extension range start only when creating a tenant. Verify both before saving. The tenant name, extension range end, limits and other editable fields can be updated later.

Import an existing Mirta PBX tenant

Use Import when a tenant already exists in Mirta PBX but has no MSPControl package link.

1. Open Voice > PBX Tenants and select Import.
2. Select an importable Mirta PBX tenant.
3. Complete the import.
4. Open the imported tenant and link the appropriate hosted organization.
5. Verify its range, limits and status before making other changes.

Import creates the MSPControl record and package link for the existing provider tenant. It does not create a second tenant in Mirta PBX.

Link a hosted organization

The organization link enables user matching, Teams integration and voice-policy checks for the customer tenant.

Only organizations not already linked to another PBX tenant in the same package are available. If an expected organization is missing from the selector, check whether another tenant already uses it.

Manage extensions

After the tenant has been saved, the edit page shows extension counters backed by current Mirta data:

• Linked: extensions with an MSPControl user link;
• Unlinked: Mirta extensions without an MSPControl user link;
• Matchable: unlinked Teams extensions whose Entra object ID matches an active organization user;
• Misconfigured: linked extensions with a detected caller-ID or DID-routing issue.

Live provider access affects extension status

MSPControl can still show stored link information when Mirta is unavailable, but unlinked and misconfiguration counts require live provider calls. The page displays a provider warning instead of treating unavailable data as a confirmed zero.

Link extensions to users

1. Select the Unlinked counter.
2. Review the extension type and proposed user.
3. For a Teams extension, confirm the user matched through the Entra object ID.
4. For a SIP extension, select the organization user manually.
5. Select the required rows and choose Link Selected.
6. Reopen the Linked list and confirm the user, extension number and type.

The bulk operation reports individual failures, so verify the result instead of assuming every selected row succeeded.

Unlink or delete extensions

• Unlink Selected removes the MSPControl user-to-extension link but does not delete the extension in Mirta.
• Delete Selected calls the Mirta provider to delete each selected extension, then removes a matching local link when the provider operation succeeds.

Deleting an extension changes the live PBX

Use Delete Selected only when the extension itself should be removed from Mirta PBX. Use Unlink Selected when you only need to correct the MSPControl user association.

Review detected configuration issues

The Misconfigured list can report:

• an outbound caller ID that does not match the authentication caller ID for a Teams extension;
• an outbound number with no matching DID in the tenant;
• a matching DID that does not route back to the extension.

Correct the underlying Mirta or Direct Routing configuration, then refresh the status.

Configure Microsoft Teams integration

Teams integration requires a linked hosted organization. From the tenant edit page, MSPControl can:

• create the required Entra application registration;
• validate and link an existing application by client ID and secret;
• show application identity, secret expiration and compliance status;
• report missing or unconsented permissions;
• rotate the application secret;
• unlink the application and clear the Mirta-side credentials.

The current compliance check expects Presence.Read.All as an admin-consented application permission and User.Read as a delegated permission. Treat the client secret as a credential and do not place it in screenshots or support tickets.

Verify Teams voice policies

When the tenant has a linked organization and Teams application, the edit page checks four Direct Routing objects:

1. PSTN gateway;
2. PSTN usage;
3. voice route;
4. voice routing policy.

Each check can report Missing, Present, Misconfigured or Unreachable. MSPControl can create the expected objects or link existing gateway, route and routing-policy identities. Linking an existing object changes what MSPControl validates; it does not duplicate that object.

Read-only Microsoft 365 organizations cannot run these checks

The voice-policy panel requires access to the customer Teams tenant. When the linked organization is configured for read-only Microsoft 365 access, MSPControl explains the prerequisite instead of attempting the policy snapshot.

Disable or delete a tenant

Use Disabled to change the tenant’s provider status without removing the MSPControl record.

Deleting a tenant calls the Mirta PBX tenant-delete operation and then removes the local MSPControl tenant record after the provider call succeeds.

Confirm provider-side impact before deleting a tenant

The reviewed MSPControl source proves that the live Mirta tenant is deleted, but it does not define or back up every child object that Mirta may remove with it. Confirm the provider-side retention and recovery behavior for your Mirta deployment before deletion. Disable the tenant when removal is not intended.

Related guides

Configure hosted voice with Mirta PBXConfigure the provider, plan resource group, quota and permissions.

Manage hosting plansAdd PBX resources and customer capacity to a plan.

Manage hosted organizationsReview the organization that supplies users and Microsoft 365 context.