Microsoft is not shy about the fact that Microsoft Teams is quickly becoming the single pane view into your Microsoft 365-driven digital workspace. However, we know that not everything we do happens in the Microsoft ecosystem, and as robust as their toolsets and features are, that’s likely not ever to be the case.  

So what’s an organization to do when you’ve got disparate tools? 

One way Microsoft is providing connections is through Microsoft Graph. Using Teams endpoints in Microsoft Graph API, we can build connectors, empowering us to get data in and out of Teams. For example, we could pull reports from something like Salesforce, create a team from another location by filling out a form, post messages in from other platforms like Service Now, and of course, get data out to other sources. As you can imagine, the demands are ever-changing, and so the solution must also be evergreen. Microsoft manages this by maintaining two versions of the endpoints in Graph API. v1.0 (live and in production), and beta, where Microsoft is playing with and experimenting with new things and seeking feedback and assistance from the community. The best and most in-demand beta endpoints then get baked into v1.0. Beta is ALWAYS changing. v1.0 is always set.  

Who is beta for?  

Essentially, Microsoft  beta endpoints are early adopters, the forward-thinking tech lovers who want the latest and greatest at their fingertips. 

Why use beta endpoints?  

Microsoft beta endpoints provide an excellent way to test out functionality and features; to discover what’s possible. Beta endpoints can be used in production to help bridge important gaps in your digital toolsets, but Microsoft does not support it. This means someone must stay on top of it, so when changes do occur in beta, and it breaks, you’re able to fix it quickly.  

How do you know what’s available when beta is always changing?  

Well, the best way to stay in the know is to go straight to the documentation.  Microsoft also maintains documentation on what’s new in Microsoft Graph. To determine whether an API is available in v1.0, you can also use the Version selector (which as of this post is a dropdown in the top of the left column).   

Another great resource is the Graph Explorer. This lets you try out queries from either sample data or you can connect to your own environment. Plus, you can select from either v1.0 or beta endpoints in the UI. 

There’s currently not significant communication when things go from beta to production. It’s often quietly released with little fanfare, and some things have been in beta for a very long, time never make it to production. To determine whether an API is available in v1.0, use the version selector, or check out the changelog.   

A popular Teams feature request is to be able to backdate messages in channels. We’re currently seeing this available via the beta version, and hopefully it will hit production level soon. 

Do you have a feature you’re dying to see go into production? Do you have something you’d like to test out? Does your team need help bringing in disparate tools into your digital workspace? A PixelMill Microsoft 365 expert would love to chat with you today!