Microsoft 365 SSO Options

This article will provide a walkthrough on activating Microsoft single sign-on in the multi-tenant side of the bvoip phone system.

Updated at January 1st, 2025

Follow the simple decision tree below to determine the path you should take for setting up Microsoft 365 SSO for your use case.

Are you setting up SSO for internal use, or resale?

Internal

 

Resale/End Customer

 
 

Follow Changing the Control Portal Subdomain to change the domain to your preference.

Then follow Setup Branded Microsoft 365 SSO for Partners.

And lastly follow Setup Microsoft 365 Single Sign-On (SSO) for Phone Systems after which your custom domain will be functional.

 

Do you want customers logging into your customized domain (White Label), their own customized domain, or the basic bvoip domain?

Single White Label Domain

 

Custom Domain per Customer

 

Generic *.bvoip.net Domain

 
 

Follow Changing the Control Portal Subdomain to change the subdomain to your preference and/or setup a full custom domain.

Then follow Setup Branded Microsoft 365 SSO for Partners 

Lastly complete the document Setup Microsoft 365 Single Sign-On (SSO) for Phone Systems for each customer phone system, and they should all be able to login to the custom domain you've created.

 

Are your customers nested in their own portals (default for Pax8), or a flat structure (default for direct partners)? If you have customers listed under System > Customers, you're nested.

Nested

 

Flat/Direct

 
 

Follow Accessing Customers as a Pax8 Reseller to get into the customer's system you're configuring.

Follow Changing the Control Portal Subdomain to change the subdomain to their preference and/or setup a full custom domain.

Then follow Setup Branded Microsoft 365 SSO for Partners under their impersonation view

Lastly follow the article Setup Microsoft 365 Single Sign-On (SSO) for Phone Systems in their impersonation view, and they should be able to use their custom domain.

 

If you're fine using the unbranded login page, you can follow Customizing the Phone System FQDN and then Simplified Microsoft 365 SSO.

Otherwise, to use the branded login page, your customers would need to be moved to the nested structure to support individual custom domains per client.

You can Creating A Support Ticket and our team can get the phone system moved under a nested customer after a brief outage, after which you can follow the Nested choice in this guide.

Follow the Activating the Microsoft 365 Integration article and then complete the Simplified Microsoft 365 SSO process.