At the moment, there is no way to list all teams using a /teams call. You always need to enter a group id (/teams/<guid>).

That is why we need to resort to
GET /groups?$select=id,resourceProvisioningOptions

to filter out all Teams in the organization. However, we cannot deduce from the response if said Team is archived or not. This can only be inferred from the /teams call.

It is not feasible / wanted / efficient to query 6000+ Teams in an organization on a regular basis to know if they have been archived through the Teams UI.

That is why a /teams/delta call would be very helpful.

Suppose my Inbox has 'Email 1', which has attachments on it.
Outlook allows me to attach 'Email 1' to 'Email 2' as an itemAttachment. I can even attach 'Email 2' to 'Email 3' to get another level of nesting.

The Graph API allows me to create itemAttachments but appears to strip out nested attachments.

For example, the following request creates an itemAttachment but strips out the nested attachments (verified via API and Outlook client)

POST https://graph.microsoft.com/beta/me/messages/{some-msg-id}/attachments
Content-type: application/json
Content-length: 200

{
"@odata.type": "#microsoft.graph.itemAttachment",
"name": "Hello world",
"item": {

"@odata.type": "microsoft.graph.message",

"subject": "foobar",

"body": {

  "contentType": "HTML",

  "content": "lorem ipsum"

},

"attachments": [

    {

        "@odata.type": "#microsoft.graph.fileAttachment",

        "name": "myfile.txt",

        "contentBytes": "some file content"

    }

]

}
}

would like to have a filter on the users api of Microsoft Graph API, where I will be able to filter the users based on onPremisesSamAccountName, which is currently not available with Graph API.

We have the internal employee id to be stored with onPremisesSamAccountName variable which is present in users API of Microsoft Graph. We are trying to filter with onPremisesSamAccountName property to filter based on the internal employee id. Currently we are not able to do that with Graph API but we really need this to be workling or would be happy if we get know any possible workarounds if available

https://graph.microsoft.com/v1.0/users?$filter=onPremisesSamAccountName eq '[some-id]'&$select= userPrincipalName,displayName,department,jobTitle,companyName,onPremisesSamAccountName,....[more list of fields for select]
The expected outcome is to show the required result but the response what we got is as follows

{
"error": {
"code": "Request_UnsupportedQuery",
"message": "Unsupported or invalid query filter clause specified for property 'onPremisesSamAccountName' of resource 'User'.",
"innerError": {
"request-id": "[request-id from request]",
"date": "[date on which request is made]"
}
}
}

The current beta version of the Graph API for SharePoint Sites, specifically the Page objects, supports GET (read), POST (create), and DELETE (delete) operations, but does not appear to have any support for PUT (update) of an existing Page.

https://docs.microsoft.com/en-us/graph/api/resources/sitepage?view=graph-rest-beta

This means that in order to make an update to a page via API, the only option is to GET the current page, update as needed in our application, DELETE the current page, and then POST to create a completely new page (losing all history, original creation date, etc.) with the same name/title... which also results in a new object ID that we have to store.

It would be a much better and more logical developer experience if there was an API method to update existing Pages the way there is for most other objects in the SharePoint portion of the Graph API.

I've confirmed this current limitation with Aaron Miao of Microsoft SharePoint Developer Support (via Premier Support) and was instructed to raise the feature request here.

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 customers environment in our system before they actually log in.

This is basically the same as the current change notifications you can create a subscription for:

POST https://graph.microsoft.com/v1.0/subscriptions
Content-Type: application/json
{
"changeType": "created,updated",
"notificationUrl": "https://webhook.azurewebsites.net/notificationClient",
"resource": "/me/mailfolders('inbox')/messages",
"expirationDateTime": "2016-03-20T11:00:00.0000000Z",
"clientState": "SecretClientState"
}

The difference being that it would work for B2C users and we can specify a changeType of "created" which is currently not supported for the "user" resource type