Microsoft 365 Community Community Demos, 9 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Outlook add-ins and Outlook REST V2 decommission

Description

In this 13-minute Developer-focused demo, the Outlook REST V2 Endpoint will be decommissioned on Nov 30, 2022. Juan Balmori lays out the program and options. Scenarios impacted – Exchange Online and some OnPrem (Hybrid) using REST APIs or Delegate Scenarios using REST. Exceptions will be granted for active Add-ins using REST. APIs specifically impacted called out in session. Action - move to the graph now and alert Microsoft to gaps on Graph Endpoint. Alternatively use Exchange Web Services (EWS). This PnP Community demo is taken from the Office Add-ins community call – February 2022, recorded on February 9, 2022.

Demo Presenter: Juan Balmori (Microsoft) | @juaneloBalmori

Supporting documents:
• Sample - Single Sign-on (SSO) sample Outlook add-in | https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/auth/Outlook-Add-in-SSO

Stay connected:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos

A

Hello, everyone swan valmori here, I'm going to give you an update for outlook, add-ins and the outlook. Rest v2, the commission. uh What's going to be the plan here, so what's going to happen for all outlook developers here in the community call or watching on demand.

A

Basically, as you probably already heard on november 30th this year, the outlook rest, 32 endpoint will be decommissioned.

A

So basically, I'm adding just a sample snippet here on the on this slide, so that you can identify that if you are using the get callback token api with that is rest parameter equals true. uh That means that you know uh this call event. I mean I'm gonna tell you what how how the other commission is gonna be about, but this at some point it's gonna stop working.

A

You know so this impacts both uh exchange online, mostly uh but you're, in exchange on prem uh on a hybrid configuration only uh you know 100 on premium, the rest is not available, but on premium hybrid, you you'll have also this problem, so the scenarios impacted is obviously if, if you want to use the rest apis as part of your outlook, adding uh this is not no longer going to be available. uh I have specific areas of the api that will get impacted, but the bottom line is the rest.

A

Apis are not going to work anymore and then the delegate scenarios also have a couple of apis that are using rest calls to to do operations on behalf of the owner of the folder. That's also, we will have an alternative for that. So basically that's the problem that we have right now.

A

So let's go a little bit more into detail about the impact, because I mean when I when we were announcing this uh the commission. You know one big concern that I that I have- and I share with the team who is owning this product- is that we really don't want to break our audience right. It's like uh we should never do that so so.

A

The good news here for everybody that is using this today is that we are going to be granting exceptions uh for this decommission for all add-ins who are using the rest endpoint before the before that the commission date before november. So, basically, if you have nothing today that is using the rest endpoint, you will still be able to using the rest endpoint until the end of support of office 2019, which happens to be october, 14th 2025. So basically, you have a few more years.

A

You know to to to move your ad in to alternatives, which is in this case the graph note, uh um I think, that's a natural progression of of of things here now. The problem is that adding is created after the commission date, so we have a way today of of of knowing what add-ins are using.

A

You know the rest end points so we'll have this list of add-ins by id, but if you're, if, if your add-in is created after the commission date, then uh you will not be able to use the rest service. No, so you need to move to either depending on on what your operations you're doing uh to the graph or to ews instead.

A

So this is all good news for everybody who is using the the apis today. Does the extension for adding supply only to no? These are for all add-ins. All add-ins that are using the rest, endpoints are not necessarily just coming from. The store are also addings that are privately released, are going to grant this exception as well. It's a good question, michael so now. The other thing that I want to comment here is oh well.

A

This is more detail about exactly what's impacted now, so we have this all these apis and I'm going to go one by one telling you what's the story here so basically, obviously, when you, when they get the get callback token async method with the is rest option, is impacted, of course, what's going to happen here, this is basically the api you use to get the rest compatible token. Obviously, if you use the property is rest, you get a rest compatible token. Otherwise you get an ews compatible token.

A

So this api is going to fail for new alien for new advance is going to fail. So basically, the recommendation here is to use the graph as an alternative. No, so we recently shipped the sso feature, and it's in fact I think uh david here himself produced a few examples on how to use the you know the single sign-on and get a graph compatible token, so that you know your admins use the graph. Instead, now I got the I I I don't own.

A

The rest end points, but what I, what I've learned from from that team is that we have now 100 compatibility between the rest, endpoint and the graph endpoint, so so that means that everything that you can do with the rest end point today is also doable with the graph. uh Of course I mean I don't know. Maybe maybe there are a few exceptions here uh at this point.

A

One of the call to actions that I have for for our communities to to just let me know if that's not the case so so that we can prioritize filling up those gaps and, of course, if you're, using ews, so ews at this moment, is that we have. We don't have any concrete plants to to deprecate so so it can be also an alternative to the graph, no uh in case.

A

So the recommendation here is try to use the graph first use the single sign on methods to to get those graph compatible tokens and use the graph. You know, and the documentation here is uh very extensive by the way so uh rest version. Obviously this this api is going to become basically obsolete.

A

We will not be able to know the rest version anymore, we're going to keep the conversion ids, so we have a few apis to convert to rest id and convert to ews id, as we think that that this apis can might be still useful for the graph in case you need to supply an id and, finally, the share properties target get address, url, which basically means the it's api that you use to get the url to make the rest column behalf of the owner of a folder.

A

Here we also need to have a graph alternative. We are using this. For, for this is very relevant for the delegate scenario right, so is there a way to check if a certain idea is in your extension list? That's always asking yes, absolutely! uh I thought please follow up with me offline and- and I was getting a list of all these add-ins uh this week, in fact, so that if you, if you can actually send me an email, we can see verify that your adding is in this list.

A

I will send you my contact in a second all right, so uh also in addition to this, there are many exchange. Your enterprise install michael there's, the extension for ryan's apply time is deploying the storage. Yes, this one can start deploy. That is no again. This is not only for store deployed audience. Enterprising play guidance will also work.

A

B

A

There any is this a manifest change? No, there are no manifest changes, so there are no manifest changes here. uh Basically, the way that this is going, I mean we still are- are thinking how we're going to do it. If we're going to fail the calls immediately or if we are going to allow them and verify that this is this was not an adding before november and and you know, contact the developers and and make sure that they make the move no, but there are no manifest changes associated with this.

A

This is going to be it's all fixed server side. That's my my hope at this point all right. So, let's move on so the bottom line here. So my my recommendation for everybody is to move to the graph as soon as you can. This is something that you know that microsoft is moving strategically, that our customers are asking. You know, I know many big and small and huge isbs who who actually their customers are asking them to stop using rest to start using ews and go to a more controlled scope level.

A

You know uh permission settings, so uh this is uh about about providing more granular security of operations. So this is the right move, so please make sure to move to the graph. For that. Obviously, you need to be checking if, if we have the requirement set identity 1.3, so the easiest way to implement a call to the graph is to use ssl. Fortunately that was shipped, uh I think, just a couple of years ago, with identity 1.3 api.

A

So if, if during the context of activation of your ad and identity 1.3 is available, it means that sso is available. Single sign-on is available in that environment, so, basically you can do the handshake. This is all handshakes and get a graph compatible token and make the graph calls now remember that the graph calls the part that was created for sso is that the admin needs to deploy the adding within the organization and and the consent happens at deployment time.

A

So the admin is the one who is in advance accepting you know the consensus of the graph scopes that you're adding requires. So the flow that that which is most of the flow of office is the flow that requires your adding to be deployed from an admin perspective.

A

It's fully, I mean the user is going to don't go against any dialogues or anything like that. It's going to be pre-consented by the admin.

A

On the other hand, if the user goes directly because you will have to to pop, you know the the consent messages to the user, so they can use it ews I mean if the requirement set 1.3 is not available. Sorry, basically, the fallback is to use ews and remember that ews is uh in in the context of all locations doesn't mean that you can call anything right.

A

It's limited to the calls that are in this link that I am showing you here it's it's I mean most. Talents are okay, using what what the functionalities that are listed in this link and then you should be okay call to action for everybody.

A

Do let us know if, if you find gaps in the graph endpoint, so I think I, the team, feel confident that that that's the case but but but you know, I want to hear from you guys if you, if you find anything that is not working as you expect absolutely let me know, and we we can work with the rest team. You know and that's what I have for today.

A

I think uh there are a few questions here on the chats that I'm going to answer.

A

uh There are a chance to know this graham will follow up with that question offline. I was referring to if the update of the app manifest and redeploy does that reset the rest compatibility of them yes like if you change the id by which your administ is making the call you're going to fall into the new adding category, so you need to be careful with that erica gold eric. How are you getting on the graph?

A

Yes, I'm not sure why people are laughing about this comment, but I will just put like with the detection of precision: is we tied to a manifestation? No, it's! Not! It's a manifest id, so we know uh there's a token that is passed uh on the call that we identify that it's coming from an add-in and from there we can identify which, which is specifically, is making that call. So it's not a manifest change. It's not the idea of the manifest.

A

Could we have a demo of a basic outlook adding using the graph in the future? I think this already exists. Pinakin david, correct me if I'm wrong, but I think we do have a pattern pattern, some practice that is talking exactly about this. You know how to do an sso authentication and then make a graph call.

A

We will make sure that you guys have all these documents so absolutely yeah about so.

B

I put a link to that sample. It kind of floated up higher in the chat, but there's a link to it. If you want to look at it.

A

Yeah, that example, is basically what you need to do, but of course this is just the first interaction that we have for the community. The first time we are talking about this with you guys uh expect. You know we're gonna be blogging about this. We're gonna be providing more documentation, you know so that you're ready. I think we we are right on time. You don't need to worry again if your ad is being used today, so that will, with exception, will be granted all right.

A

So I think there are no more reservation questions here, uh but again move to the graph guys. That's my my advice here and thank you very much david.

B

All right, thank you juan. This is uh really great news. I think, hopefully I'd answer a lot of people's questions that they've had because I know uh folks been asking about this for a few months, so uh very cool.