Features

    Retrieve SSO Client ID

    The VoIP Help Page Team·4 min read·Last updated: March 14, 2026

    ### Scope

    This article outlines the setup of your O365 and GSuite SSO with your Hosted PBX service. You will need to provide the credentials to our onboarding team to get set up. To enable SSO for a domain, see Enable SSO for a Domain

    Requirements


    1. 1

      Login to https://portal.azure.com  with your developer account.

      NOTE: If you haven't set up Office 365 for your domain, Microsoft provides a detailed guide at: https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-web-app-sign-user-overview

    2. 2

      Select Azure Active Directory service.

      1. 1
        Use the search function to find it, if it is not visible on the dashboard.
    3. 3

      Select App registrations from the side pane.

    4. 4

      Register a New Application (if not previously performed) by clicking the + new registration button/link in the center pane.

    5. 5
    6. 6

      Select the previously created App registration by clicking the Display name.

    7. 7

      Copy the newly created Application (client) ID from the data set in the center of the pane and retain it for a future step.

    8. 8

      Select Authentication from the side pane.

    9. 9

      Under Platform Configurations choose +Add a platform.

    10. 10
    11. 11

      In the resulting Configure Web pane, enter one of the required Redirect URLs, the Logout URL and select Implicit Grant for both Access tokens and ID tokens. When complete click Configure.

    12. 12

      Redirect URI: https://<PBX FQDN>/portal/msal.php

    13. 13

      Logout URL: https://<PBX FQDN>/portal/login/logout

    14. 14
    15. 15

      Add the remaining required Redirect URLs by using the Add URI link at the bottom of the Web platform box.

      https://cdn.elev.io/file/uploads/VYtmahJgiiNC4Q7omNSQkjr0mA1mIm3IhwV3m1DP_lg/NVByEuDA_YyOjlzk_crZ-FfyM_vglQqqenG9Gw88pmo/1595907617179-Uvw.png

    16. 16

      ALL required Redirect URIs are below:

           \*  https://<PBX FQDN>/portal/msal.php (Added in step 10)

          \*   https://<PBX FQDN>/analytics/

          \*   https://<PBX FQDN>/video/

          \*   https://<PBX FQDN>/webphone {no trailing slash)

          \*   https://<PBX FQDN>/

    17. 17
    18. 18

      Click Save at the top of the page. Your Office 365 SSO service will now be fully configured and enabled on Azure.

      NOTE: You should have "personal Microsoft accounts" listed in the "Supported account types" section. If missing, navigate to the Manifest and set the 'signInAudience' parameter to "AzureADandPersonalMicrosoftAccount"

    19. 19

      Provide the Application (client) ID to your onboarding team to finish setup


    1. 1

      Login to https://console.cloud.google.com// with your developer account.

      NOTE: If you haven't set up G Suite for your domain, Google provides a guide at: https://support.google.com/domains/answer/6069226

    2. 2
    3. 3
    4. 4

      Set the Application Name to your preferred display name.

    5. 5

      Add your top-level domain to Authorized Domains.

      NOTE: This section offers control over the application's display name, support email, and logo. These settings may be important to your branding but are not required.

      If you change your logo image Google will start a manual review process that can take up to 6 weeks. They might also require a link to your privacy policy. There are several free generators online that can assist.

      https://cdn.elev.io/file/uploads/VYtmahJgiiNC4Q7omNSQkjr0mA1mIm3IhwV3m1DP_lg/1PnpQTh6wRY5nUTtsTSp1PwCPmNV3L_XxVycExbo5_I/1595913967277-kjQ.png

    6. 6
    7. 7

      Select Web application.

    8. 8

      Set Name as desired.

    9. 9

      Under Authorized JavaScript origins, add your portal's hostname (EG: https://manage.niftywidgets.co)

    10. 10
    11. 11

    Was this article helpful?