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. Add support for wWWHomepage

    Microsoft Graph cant return the wWWHomePage property that people know from regular AD. We need to access this field in a business case and cant do so, because of the current limitations.

    Please add support for wWWHomePage on the User object!

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

    We’ll send you updates on this idea

    4 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add Deleted By to Delta Query Indicating Compliance or Retention Delete

    It would be great to know what process deleted an item in the Delta Query. This way we can tell the difference between a Compliance/Retention delete and a user deletion action. That way third party apps can take action on items deleted by policy.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  3. Extensions Permission

    This affects all resources that support extensions but let’s take the User resource as an example:

    Extending the User resource currently requires an entire User Profile read/write consent (User.ReadWrite).
    We only want to read and write additional data that we provide to the User resource and not modify the entire resource. Users might be hesitant about consenting to Apps that could potentially corrupt their entire user profile.

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

    We’ll send you updates on this idea

    2 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  4. Expose additional O365 subscription and user data

    Data that can be fetched using Get-MsolSubscription is not exposed via Graph API: CreatedDate, IsTrial, RenewalDate. Also, when fetching users, there are fewer user fields available with GraphApi than with Get-MsolUser: WhenCreated, LicenseReconciliationNeeded, IsLicensed, Blocked... It would be nice to expose this data related to license usage.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable combining filter and orderBy on users endpoint

    I want to show my customers a list of users ordered by their name and all disabled users or guest users in AD should be filtered out.

    You can't do this kind of requests with the users endpoint which is quite bad if you want to create an app for a global company.

    So please enable the combination to filter and order users so that we can create great apps using the graph api.

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

    We’ll send you updates on this idea

    In Beta  ·  1 comment  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  6. When will v1.0 /users response return full profile like beta???

    Hi can someone confirm that the v1.0 /users endpoint only returns basic profile while beta does now?

    If so when will this prod endpoint return the extended profile information when querying against the /users endpoint?

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

    We’ll send you updates on this idea

    1 comment  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow MS Graph proxyAddress filters to specify endsWith() and contains()

    Currently there is support for startsWith and eq filters on proxyAddresses. However there is no way to search for proxyAddresses that endsWith or contains a string. E.g. finding users with a proxyAddress in a specific domain.

    $filter=proxyAddresses/any(x:endsWith(x,'@acme.com'))

    See this thread for more information: https://stackoverflow.com/questions/46588870/filtering-on-proxyaddresses-with-microsoft-graph-api-that-endswith-or-contains-a

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

    We’ll send you updates on this idea

    8 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →

    This work is on the backlog and currently isn’t scheduled. The feature will be updated here once dev work is started. -EY

  8. Is there some office365 graph API that being able to know whether the user's mailbox is in cloud or on-premise?

    For a hybrid exchange deployment, some users could be assigned the license for exchange, but the according mailbox may still be in onpremise environment.
    And we trying to call "https://graph.microsoft.com/v1.0/users/?$select=assignedLicenses,mail,id,displayName,userPrincipalName" to get some details of the users in the specific tenant, however, there is no way to tell whether the user's mailbox is in cloud or on-premise.
    So, is there some office365 graph API that being able to know whether the user's mailbox is in cloud or on-premise?

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  9. Get User Detail (Office 365 Activations) JSON not formatted properly

    JSON output from Graph beta API should provide string for lastActivatedDate. However null value is retrieved if user has not activated respected product license.
    This inconsistency causes data processing failures in Microsoft Flow. The 'Parse JSON' action fails with "Invalid type. Expected String but got Null." for lastActivatedDate property, as JSON schema defines string type for this property.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support result pagination in Get-AzureADUser

    The Get-AzureAdUser cmdlet does not support any pagination. The only option is -Top nnn. It appears that the underlying REST API does support pagination, so this should be a matter of exposing that support in the cmdlet.

    The problem is with large Active Directory instances which currently require -All $true - which consumes a lot of memory (and therefore doesn't work in an Azure Runbook due to the 400MB limit).

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  11. Showing significant other value in spouse name

    I have put significant other value into contact from office outlook, but In the API it showing in spouseName name field.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  12. To be able to create customized API permissions

    To be able to customize API permissions. For example, give logic app only permissions to make changes to guest user accounts, while excluding member user accounts

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  13. show administrators

    Search for all administrators within AzureAD. The purpose is to find if your number of Admins has changed, or if an admin doesn't have MFA enabled, or it has become disabled.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  14. Azure AD Redeem invite / Displayname

    I invite a user to AAD using the MSGraph API. The user recieves a custom e-mail with the redeem url.

    But at the redeem page you get to fill in your displayname which seems to be prefilled with the front part of the e-mail account. Or it should be possible to pass a hint for this field or it should take the displayname of the user account created by createinvitation in AAD.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  15. Ability to filter on collection type properties (e.g. find all users with skill X)

    In order to, for example, filter users by a certain skill you cannot do only one REST call now.

    From stackexchange:

    "Filter on collection type properties is represented as below:

    https://graph.microsoft.com/v1.0/users?$filter=skills/any(c:c eq 'Javascript')

    However, filter on skills property is currently not supported. You can place a request in uservoice site."

    I would like support for this /any command, specifically for skills but for all queries would be great too.

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

    We’ll send you updates on this idea

    8 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support assistant attribute via Graph API

    Please expose the assistance attribute via Graph API. Because on Active Directory this is a reference attribute, probably we need something similar to the manager attribute.

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

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  17. Remove User Picture

    Hello,
    It would be good if you add the possibility to remove the user picture of an user.

    Currently with the Graph API (https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/api/profilephoto_update) we can get the picture and update the picture but we cannot remove the picture (like with powershell Remove-UserPhoto)

    Thanks

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

    We’ll send you updates on this idea

    1 comment  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  18. Missing initials when filtering/selecting api/users

    Please add initials attribute to the user object

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

    We’ll send you updates on this idea

    2 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  19. 7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow filtering users by officeLocation

    While filtering works for some attributes like department it doesn't work for officeLocation, which sadly I need for my use case.

    GET https://graph.microsoft.com/beta/users?$filter=officeLocation eq 'Gaithersburg, MD'

    Returns:
    {

    "error": {
    
    "code": "Request_UnsupportedQuery",
    "message": "Unsupported or invalid query filter clause specified for property 'officeLocation' of resource 'User'.",
    "innerError": {
    "request-id": "641beedd-4df5-4b97-b6b5-4f574c382d08",
    "date": "2017-07-26T18:32:39"
    }
    }

    }

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

    We’ll send you updates on this idea

    4 comments  ·  Users  ·  Flag idea as inappropriate…  ·  Admin →

    This capability is now available in Microsoft Graph public preview. It’s not currently documented.

    NOTE: you’ll need to use a custom HTTP request header ConsistencyLevel: eventual and request $count=true as well, to enable this query capability.

    GET ../beta/users?$filter=officeLocation eq ‘SomeLocation’&$count=true
    ConsistencyLevel:eventual

    See also related queries in the changelog entry https://docs.microsoft.com/en-us/graph/changelog#identity-and-access-azure-ad

  • Don't see your idea?

Feedback and Knowledge Base