Today, we’re excited to announce that in response to your feedback, we’re changing the changelog! You will find the new, redesigned changelog on the Microsoft Graph Dev Center.
We are pleased to announce the general availability of resource-specific consent and the APIs to read channel messages. Enabling you to build apps that can read messages and manipulate channels, without needing to beg an admin for access to the entire tenant.
We are excited to announce that Microsoft To Do API is now generally available in Microsoft Graph worldwide. Previously, you could consume these APIs through the beta endpoint but now you can access them through the production v1.0 endpoint.
Announcing the beta release of the import capabilities in Microsoft Teams. These new capabilities give you the ability to import channel messages into a new team, specify the message sender and timestamp and link to files.
We are retiring the includeProperties property currently on the Microsoft Graph beta endpoint as of January 1, 2021. If your Microsoft Teams app currently uses the includeProperties resource, please update it immediately to use includeResourceData to ensure your code still works.
We're excited to announce that Microsoft.Identity.Web is now generally available. Microsoft.Identity.Web brings a renewed, simplified, end-to-end experience for developers to build secured-by-default web apps or web APIs, possibly calling Microsoft Graph or other web APIs.
Today we're announcing an upcoming breaking change to developers using the Microsoft Graph Users API. The Users API enables admins to get and set properties associated with user objects in Azure AD. This change will be rolling out to all tenants by October 5, 2020.
What is the change?
This bug fix will prevent Microsoft Graph updates to the ...
Back in February we announced the public preview of change notifications for Teams messages and we are excited to share we have now moved the change notification for Teams to general availability. This was one of the most common requests made in UserVoice, and we heard it from developers who wanted to listen to Teams messages in near-real time...