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
This is in the backlog along with some other properties we are considering for exposure on the user resource.
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
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
We do not have this started yet, but its in our plan due to other priorities. ^JT
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
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
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
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.
See this thread for more information: https://stackoverflow.com/questions/46588870/filtering-on-proxyaddresses-with-microsoft-graph-api-that-endswith-or-contains-a78 votes
This work is on the backlog and currently isn’t scheduled. The feature will be updated here once dev work is started. -EY
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
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
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
I have put significant other value into contact from office outlook, but In the API it showing in spouseName name field.1 vote
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 accounts3 votes
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
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
In order to, for example, filter users by a certain skill you cannot do only one REST call now.
"Filter on collection type properties is represented as below:
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
This item is still in the backlog. In the meantime we are researching some other options for this. Will provide an update shortly.
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
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)
Please add initials attribute to the user object2 votes
Hi Joseph, can you give some examples of the API you would like to call and the expected results?
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'
"message": "Unsupported or invalid query filter clause specified for property 'officeLocation' of resource 'User'.",
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
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?