Microsoft Graph Feature Requests

Welcome to the Microsoft Graph UserVoice! Do you have an idea or feature suggestion based on your experience with Microsoft Graph? Please share these with us by submitting your idea below or voting up ideas submitted by other users. This forum will be directly monitored by the Microsoft Graph engineering teams who are working on new features every day.

If you have feedback on a specific API service, please choose the corresponding category. Please submit any broad ideas related to Microsoft Graph or ideas across more than one service to the “General” category.

This site is only for feature suggestions and ideas! If you need technical help, please go to the Microsoft Graph StackOverflow or if you have a Premier support contract raise a support ticket.

For more information on Microsoft Graph, please checkout https://graph.microsoft.com.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Restrict permissions to app-only Azure AD applications consuming Office 365 services on resource level

    Large organization start leveraging the Graph API to provide integrations between their third party applications and Office 365. In such companies it is common to delegate the development of integrations from the central IT organization to other business units.
    The current app-only permission priviledges are not appropriate for such types of setups since there is currently no way to limit the permissions for that app to a specific resource in Office 365. This makes such use cases impossible to implement.

    As an example we could consider SharePoint Online. Whever a business unit has to develop a daemon tool that exchanges…

    419 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    51 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →

    Work has started. We plan to build an experience where end users and administrators can pick a specific resource to grant consent to, such as a specific group or site. This will be programmable through Microsoft Graph API.

  2. An Application should be able to read its own manifest

    By default an Application should be able to read its own manifest, getting access to «requiredResourceAccess» (to know what permissions have been assigned to the application) and to «passwordCredentials» (to know the App secret expiration date).
    This would be useful to let the customer know if there is a permission issue or that the App secret will expire soon.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support Re-register for MFA for a user with Graph

    Admins and apps should be able to programmatically enforce "Re-register MFA" for a user. This is missing in Graph.

    See also https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userdevicesettings
    "Require Re-register MFA makes it so that when the user signs in next time, they're requested to set up a new MFA authentication method."

    Thx, Toni

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  4. Variable throttling limits depending on license or app

    When we need to get data out of O365 speed is important. The throttling is excessive. Suggest something in the line of E3 4X  standard E5 10X standard. You could even limit the increase to the app IDs of certain level of partners.

    18 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  5. Provide a programmatic way to request Azure MFA verification of users.

    Provide a programmatic way to request verification of users (e.g. push, sms, etc) via Azure MFA.

    I would use this in two ways:

    a. Custom step-up authentication in our custom applications, where we want to do a push auth, but we don’t want the user to enter a password.

    b. Allowing help desk analysts to authenticate users remotely before providing assistance.

    A competitor has a similar restful API:
    https://duo.com/docs/authapi#/auth

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  6. add 'Status' and other missing attributes to the riskDetections endpoint

    There are some very useful attributes present in the RiskySignIns report downloadable from the Azure AD admin center Security section. The most important one in my mind is 'Status', but there is also 'Application' and 'Sign-in error code' and 'Failure' and others. It would be very useful to have these included in the response from the riskDetections endpoint.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  7. Primary Refresh Token

    Add identifiable Primary Refresh Token (PRT) data to the Azure Activity Directory (AAD) sign-in logs so detections can be on Pass-the-PRT.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  8. API to retrieve application SAML SSO User Attributes & Claims data

    Need API to get Enterprise application's SAML configuration data. Currently certain data can be get through applications or servicePrincipals API, but not full SAML configuration.

    For example User Attributes & Claims. ( I have checked https://graph.microsoft.com/v1.0/servicePrincipals/<appid>/claimsMappingPolicies but it always return empty result ).

    We have hundreds of enterprise applications with SAML SSO configured in our tenant, it's difficult to audit all those SSO configurations without API.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  9. Graph API support for finding out shared mailboxes and Public folders

    Graph API support for finding out shared mailboxes and Public folders.

    This info is accessible by powershell only.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  10. Expose API to update primary (MFA used) Email on AAD B2C. This is critical when AAD B2C not the SOR. 100K Users affected.

    Expose API to update primary (MFA used) Email on AAD B2C. This is critical when AAD B2C not the SOR. 100K Users affected currently. (Ernst & Young)

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add $count and $select capabilities to all auditLogs resources

    Analyzing logs is heavy on data in large environments. It would make a lot of sense to make it possible to use $count and $select for these kind of queries.

    Reduce Microsoft Graph load, bandwidth usage, and client resource usage, by making $count and $select available to all resource types that falls inside auditLogs.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support Managed Identity

    Various other resources support the use of Managed Identity, like Azure KeyVault does. This prevents the hassle of juggling secrets. The Graph API could use this as well.

    The current (clean) workaround seems to be to use Azure KeyVault with Managed Identity, and then get the client secret used for the Graph API from there.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow Dynamic scoping to Application access policies in Exchange.

    When Using ApplicationAccessPolicy to limit Application permissoins in Exchange, you can only use Mail Enabled security groups. You cannot create a dynamic mail enabled security group. This creates a problem when trying to limit an application to a dynamic group of mailboxes. (Application Permissions)
    We have a need to manage applications on a country level. An application in one country may be only approved to work on mailboxes in that country. We have not found a way to secure GraphAPI Application access within Exchange to only the mailboxes in that country because there is not a way to dynamically manage…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  14. Graph API Beta - Un-assign Policy from Service Principal

    Today there is an endpoint to assign Azure AD Policies to service principals, but there is no endpoint to un-assign a policy from a Service Principal.

    Here is the endpoint to assign a policy:
    https://docs.microsoft.com/en-us/graph/api/policy-assign?view=graph-rest-beta

    Here is a link to the powershell cmdlet for unassign policy:
    https://docs.microsoft.com/en-us/powershell/module/azuread/remove-azureadserviceprincipalpolicy?view=azureadps-2.0-preview

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →

    First note is that we now have named policies rather than a single policy type. This change was made in February, just after your post. See https://docs.microsoft.com/en-us/graph/changelog#identity-and-access-azure-ad-3

    The docs have recently been updated to ensure that the Add, List and Remove topics are present. Please see and example:
    https://docs.microsoft.com/en-gb/graph/api/serviceprincipal-delete-claimsmappingpolicies?view=graph-rest-beta&tabs=http

    While policies are ALSO in v1.0, you can’t currently assign them to servicePrincipals as we only just added this to v1.0. An update will go out in a couple of weeks to enable add, list and remove typed policies to/from a servicePrincipal.

  15. Add a way to refresh the accessPackageResource object's properties.

    Currently, resources in the Entitlement Management resource catalog get their properties from the resource when it is added to the catalog. If the resource's name changes, it becomes out of sync with the catalog causing confusion. Ideally, it would be best if the properties were synced. However, a workaround could be to add another method to the graph API accessPackageCatalog resource type to refresh the properties on all the accessPackageResource objects contained in the catalog.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  16. orgContacts should support "msExchHideFromAddressLists"

    Full story: Our goal was to query an API that is "like" the tradional GAL. In theory the GAL is just a combination of users and contacts, so we thought that this would be ok-ish just get all users first and then query orgContacts.

    Unfortunately we discovered that the orgContacts API (https://docs.microsoft.com/en-us/graph/api/orgcontact-list?view=graph-rest-1.0&tabs=http) will return all contacts from the tenant.
    In our tenant some contacts are flagged with msExchHideFromAddressLists and this would be a NoGo four our application to surface such "hidden" contacts. We didn't found a way to filter them.

    It would be nice to have this "old…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow notification for user registration (creation) in Azure B2C tenant

    Applications in a B2C workflow need to be able to know when new users have registered.

    In our current flow a user purchases a license to our product. The billing software will call a webhook to our application which triggers a transactional email with a registration link (this is an azure B2C registration link). We need to be able to know once the user has completed registration (e.g. we need to be able to subscribe to a "user created" event that calls our application whenever the user signs up). This is important to send a welcome email and bootstrap the…

    12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  18. create retention event

    Hi,

    There is the ability available to create an event using REST api - https://docs.microsoft.com/en-us/microsoft-365/compliance/automate-event-driven-retention?view=o365-worldwide
    However this only seems to work with basic authentication which some Orgs dont allow.
    Can you extend Graph api to provide permissions for this also?

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow Application Permission to privilegedApproval API

    Allow Application Permission to privilegedApproval GraphAPI to allow create other interfaces to approve PIM Requests.
    (Or just put Teams approval function for PIM)

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow Exchange Application Access Policies to scope access to non-user mailboxes, e.g. Shared Mailboxes

    Allow Exchange Application Access Policies to scope access to non-user mailboxes, e.g. Shared Mailboxes, Resource Mailboxes, etc. Currently the documentation for the New-ApplicationAccessPolicy cmdlet indicates that policy scopes (PolicyScopeGroupID parameter) "only accepts recipients that are security principals. The following types of recipients are not security principals, so you can't use them with this parameter: Discovery mailboxes, Dynamic distribution groups, Distribution groups, Shared mailboxes".

    We have an urgent need to be able to scope Graph API based non-interactive applications to only be able to access specific Shared Mailboxes, not all mailboxes in the tenant. We thought we could use App Scoping…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Identity and Access  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base