Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Sep 23, 2019 in Development, Microsoft Teams

Using the Microsoft Teams BETA Graph API calls? They may be about to break on you…  3 API calls going away soon

Using the Microsoft Teams BETA Graph API calls? They may be about to break on you… 3 API calls going away soon

The beta API endpoint of Microsoft Graph is, by nature, home to some of the more cutting edge, newer and (I think) more interesting things that one can use Graph for.

That does come with some risks though: Microsoft say that any APIs in the /beta namespace are “subject to change. We don’t recommend that you use them in your production apps.”

That’s definitely true right now for anyone using the beta endpoint for working with Microsoft Teams. 3 of the API calls are about to be removed.

Which calls are being removed?

The following API calls are being removed:

It’s important to note that no functionality is actually being taken away – it’s just that the data is available elsewhere. Naming conventions and general tidying up seems to be reason for making these changes now, before they go into the v1.0 namespace and get effectively “locked”.

When will these calls stop working?

All 3 of these API calls will stop working in the last week of September. That starts today!

What should I do?

These changes will require code to change. It should be the case that just the URLs need to be slightly adjusted, the response body should stay the same. However, doing nothing is not an option because the old URLs will stop working soon and if your application relies on them then you will start seeing errors.

 

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams