Start Ms access resource not updating

Ms access resource not updating

Enterprise developers and software-as-a-service (Saa S) providers can develop commercial cloud services or line-of-business applications, that can be integrated with Azure Active Directory (Azure AD) to provide secure sign-in and authorization for their services.

For information about getting authorized access to Office 365 via Microsoft Graph, see App authentication with Microsoft Graph.

The following steps show you how the consent experience works for both the application developer and user.

This article shows you how to add, update, or remove an application's registration in Azure AD.

You learn about the different types of applications that can be integrated with Azure AD, how to configure your applications to access other resources such as web APIs, and more.

This registration process involves giving Azure AD details about your application, such as the URL where it’s located, the URL to send replies after a user is authenticated, the URI that identifies the app, and so on.

Once your application has been registered with Azure AD, it may need to be updated to provide access to web APIs, be made available in other organizations, and more.

This section covers the configuration steps required to provide the secret key your client's credentials.

Additionally, before a client can access a web API exposed by a resource application (such as Microsoft Graph API), the consent framework ensures the client obtains the permission grant required, based on the permissions requested.

You can select from two types of permissions for each desired web API: You can develop a web API and make it available to client applications by exposing access scopes and roles.

A correctly configured web API is made available just like the other Microsoft web APIs, including the Graph API and the Office 365 APIs.

For a complete discussion on scopes exposed by Microsoft Graph API, see the Permission scopes | Microsoft Graph API concepts article.