microsoft-graph
2 TopicsHow to define source IPs from Microsoft Graph service?
Hi, We need to setup MS Graph webhooks to points to our end points on our own servers. Question is., how this session could be hardened? Microsoft has published these network lists: Microsoft 365 Common and Office Online And on the ID 56, there is the following subnets: 20.20.32.0/19, 20.190.128.0/18, 20.231.128.0/19, 40.126.0.0/18, Are these the source IPs for what Graph is using? Or is it the other site Microsoft has published: Other endpoints not included in the Office 365 IP Address and URL Web service On there they have ID 23 Microsoft Graph Change Notifications. And tons of networks 😄 Also, when the connection is established from Graph to our servers, is there a way to identify the traffic on the header level? E.g. can I set certain GUID which will be always used? Is there something else what should be taken care?1.1KViews0likes0CommentsTeam provisioned without graph access
Hi, I've noticed that every so often when we create a new team via the Teams client, the newly created team will not be provisioned correctly. Typically once a team is provisioned you can get the root site for the team using the following graph query: https://graph.microsoft.com/v1.0/groups/{teamId}/sites/root However, we have observed on numerous occasions a provisioned team does not return the root site using the above graph query. The site itself is still accessible however using the above graph call return an error like below: { "error": { "code": "ResourceNotFound", "message": "Resource is not found.", "innerError": { "date": "2023-05-16T14:36:41", "request-id": "cfa4b716-4599-4c2f-93bd-f4604d1d5fbf", "client-request-id": "308ff383-5102-a049-88e2-eb1ba5e70557" } } } Additional Details: - Sometimes the site is accessible via the graph for a short period of time and then becomes inaccessible again.1.6KViews0likes4Comments