Skip to main content

Microsoft Entra/Azure Portal: App registration pane versus Enterprise application pane

Difference between registering an application in the app registrations pane and adding an application in the enterprise applications pane in Microsoft Entra admin center or Azure portal.

App registration is a way of reserving an app and URL with Azure Active Directory (Azure AD/Microsoft Entra), allowing it to communicate with Azure AD, hooking up any reply URLs, and enabling Azure AD services on it. When we have an application that we're developing and want to integrate it with Azure, we need to register our application in app registrations, where we'll configure the reply URL, logout URL, and API access, if needed. When we register our application, Azure AD assigns a unique application ID to it and lets us add certain capabilities, such as credentials, permissions, and sign-ins. The default settings allow only users from the tenant under which our app is registered to sign in to your application.

App Registration Pane
App Registrations Pane


New App Registration screen
New App registration screen


It's possible to confuse the Enterprise applications pane with the App registrations pane because the enterprise applications pane contains the list of our service principals. However, the term Enterprise app generally refers to applications published by other companies in the Azure AD gallery that can be used within the organization/tenant.

Enterprise applications screen
Enterprise applications screen

For example, if we want to integrate Facebook and manage single sign-on (SSO) within our organization, we can integrate it from the enterprise applications dropdown list in the applications pane. Our own applications will also be represented in the enterprise applications pane as service principals, which are instantiations of our applications in the tenant.

The following screen shows the Azure AD gallery which is opened when we click New Application from Enterprise apps screen.

Azur AD Gallery - Enterprise apps
Azur AD Gallery - Enterprise apps


If we don't find the application in the gallery, we can create out own Enterprise application by clicking the Create your own application from the Azure Ad Gallery page:

Create your own application - Enterprise apps
Create your own application - Enterprise apps

Labels:

Comments

Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more