Description: The purpose of this article is to guide you through the process of adding Ooma to Azure AD as a non-gallery application.
To begin, you need to add the application for which you want to set up SSO to your Azure account. To accomplish this, navigate to the Home page of the Azure Portal and activate the "Enterprise application" feature. If, for any reason, you are unable to locate it, you can use the Search bar located at the top of the page.
After clicking on this button, a new window will appear displaying a list of existing applications that are configured to utilize your Azure AD tenant as their Identity Provider (IdP).
An Azure AD tenant represents a specific instance of Azure AD that is a single service endpoint devoted to a single organization or tenant. It serves as a unique identity and access management service provided by Microsoft. An Azure AD tenant allows organizations to manage user identities, access to resources, and various security features within the Azure ecosystem. It operates as a centralized directory and authentication service, catering to users, applications, and services affiliated with the organization's Azure environment.
When accessing this section of the Azure Portal for the first time, it is probable that the Table of Existing applications will be empty. To create a new application, simply click on the "New Application" button.
Upon clicking this button, a new window will open, presenting the Azure AD gallery of applications that are widely popular among users. These applications have pre-configured patterns, which you can conveniently access by clicking on the corresponding card featuring the desired application's logo.
In our case, the Ooma Enterprise application does not have a standardized configuration pattern in the Azure AD ecosystem. Therefore, you will need to integrate it manually. To begin the integration process, click on the "Create your own application" button.
Upon clicking this button, a side menu will appear within the window. In this menu, you should provide the name of your application and select the checkbox labeled "Integrate any other application you don't find in the gallery (non-gallery)". By selecting this checkbox, you will indicate that the newly created application is not part of the gallery.
After entering a name for your application, the system will generate a list of suggestions based on the gallery applications that closely match your application. These suggestions can help you determine if your application has already been recognized as a gallery application and if a pre-configured pattern is available for it.
If you do not see our application in the suggested list, click on the "Create" button to proceed to the next step.
After a brief processing time, indicated by a visual cue, a new window will open, displaying a list of parameters for the newly created application.
In this section, you have the option to configure a comprehensive list of parameters for the newly created application to be utilized within the Azure ecosystem. However, for the purpose of this user guide, we will focus solely on activating the SSO feature for Azure AD and Ooma Enterprise to serve as the IdP and SP respectively.
To accomplish this, find the "Single sign-on" option in the menu on the left-hand side and click on it.
After clicking this button, the main area of the page will transition to a different interface. Among the available cards, select the "SAML" card that has appeared.
A list of new parameters organized into cards will be displayed in the main area of the "Set up Single Sign-On with SAML" page.
From this point onward, the configuration of the SSO integration should be initiated. However, due to the complexity of the process, which involves navigating between two applications (Ooma and Azure AD), it is beyond the scope of this article to provide a comprehensive guide.
If you are interested in learning how to configure this SSO integration, please refer to the next article for detailed instructions:
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article