Try ShortPoint nowWith ShortPoint Microsoft Graph API connection, you can display the dynamic content from Microsoft Office 365 applications, SharePoint sites, and other sources. Supporting the Microsoft Graph URL opened the door for many new connection types that are provided by Microsoft.
There are currently more than 90 use cases supported by the ShortPoint Microsoft Graph API connection. Despite this great number, it is not possible to support all types of Graph URL resources that are available on Microsoft's Graph URL documentation. In this article, we will tell you more about supported and non-supported endpoints of this ShortPoint connection type.
Note: The ShortPoint Microsoft Graph API connection is coming soon. Watch out for announcements about its release.
What endpoints are supported by ShortPoint Microsoft Graph API connection?
ShortPoint supports only the endpoints that fulfill the following conditions:
- The endpoint request type is 'GET'.
- The endpoint supports the 'Delegated' permission type.
- The required API Access permission is already approved
Learn how to manage Microsoft Graph permissions on the API Access page by reviewing this Microsoft article.
Note: Some use cases support and run with Delegated permission types but have required API Access permissions that are outside the scope of ShortPoint's permission requests. Check out information in the Delegated Permissions Exceptions: Unsupported Endpoints part of this article to know more.
Endpoint examples
All three requirements for an endpoint must be met. If any condition is not satisfied, the endpoint is not supported. Let's examine some endpoint examples to determine whether or not you can use them with the ShortPoint Microsoft Graph API connection type.
Supported endpoint
One of the use cases that ShortPoint supports is List users. You can visit the respective Microsoft documentation and confirm this by checking the Permissions and HTTP request sections.
We can use the List users endpoint as it's a GET request and accepts a Delegated permission type. For permissions, User.Read.All and Directory.Read.All are listed as supported permissions in the API Access page for the ShortPoint package. All you need to do is ensure these permissions are approved.
Info: We have a list of all available use cases for the Microsoft Graph API connection, the permissions they require, and additional parameters to run them. Check it out in the Microsoft Graph API: Use Cases article.Non-supported endpoint
One of the endpoints that ShortPoint does not support is Update Message. If you check the respective Microsoft documentation, you will see that the permission type is "Delegated"; however, the HTTP request is "PATCH" and the Mail.ReadWrite permission is not within the scope that is supported. This means that two of the three conditions are not met; hence, the Update Message endpoint is not supported by the Microsoft Graph API connection type.
Delegated Permissions Exceptions: Unsupported Endpoints
Many use cases support and run with GET HTTP requests and Delegated permissions. However, our Delegated permissions token has limited permission scopes. Only certain delegated permissions work with the Microsoft Graph API connection type, and functionality also depends on whether the API Access request is approved. These permissions include:
- Contacts.Read
- Directory.AccessAsUser.All
- Directory.Read.All
- Mail.Read
- Notes.Read.All
- OrgContact.Read.All
- Policy.Read.All
- Reports.Read.All
- SecurityActions.Read.All
- Tasks.Read
- User.Read.All
To maximize the benefits of the Microsoft Graph API Connection for users, we have prepared a comprehensive list of use cases to choose from. You can review our article Microsoft Graph API: Use Cases, for more information. There, you will also find the use cases with Delegated permissions that are supported by this ShortPoint connection.
That's it. Happy Graph connecting!
Related articles:
