Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update example code of how to call getSharedPropertiesAsync without using the deprecated REST token obtained via getCallbackTokenAsync. #3507

Open
CameronDwyer opened this issue Jun 22, 2022 · 3 comments
Assignees
Labels
Area: Outlook Feedback on Outlook content Status: in backlog Issue is being tracked in the backlog but timeline for resolution is unknown Type: doc request Request for new documentation or updates/enhancements to existing documentation

Comments

@CameronDwyer
Copy link

The example code on shared mailbox scenarios uses the deprecated getCallbackTokenAsync approach to obtain a REST token to be able then call getSharedPropertiesAsync. https://devblogs.microsoft.com/microsoft365dev/outlook-rest-api-v2-0-deprecation-notice/

Please show supported example of how to call getSharedPropertiesAsync without using a REST token obtained via getCallbackTokenAsync.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ghost ghost added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label Jun 22, 2022
@AlexJerabek
Copy link
Collaborator

Thanks for the sample request @CameronDwyer. Let me tag @samantharamon to help answer.

@AlexJerabek AlexJerabek added Area: Outlook Feedback on Outlook content Type: doc request Request for new documentation or updates/enhancements to existing documentation Needs: attention 👋 Waiting on Microsoft to provide feedback and removed Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP labels Jun 22, 2022
@samantharamon
Copy link
Contributor

Hi @CameronDwyer,

Thanks for bringing this to our attention. We'll be working on updating any documentation that mentions REST. I've added your sample request to our list and will let you know once the sample is available.

@samantharamon samantharamon added Status: in backlog Issue is being tracked in the backlog but timeline for resolution is unknown and removed Needs: attention 👋 Waiting on Microsoft to provide feedback labels Jun 23, 2022
@samantharamon
Copy link
Contributor

Thank you for your patience, @CameronDwyer. We're still looking into providing an alternative approach to using a REST token, but I wanted to provide an update on the decommission as a whole. Please be advised that active add-ins that use the REST service will be granted an exemption to keep using the service until extended support ends for Outlook 2019 on October 14, 2025. This includes new add-ins that are developed after the decommission date in November. This update was announced in this month's Office Add-ins community call (we're currently updating Use the Outlook REST APIs from an Outlook add-in with this update). Additional questions raised by the community during the call will be answered in a blog post and a link will be posted to Microsoft Office Add-ins community call, so watch out for that, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Outlook Feedback on Outlook content Status: in backlog Issue is being tracked in the backlog but timeline for resolution is unknown Type: doc request Request for new documentation or updates/enhancements to existing documentation
Projects
None yet
Development

No branches or pull requests

3 participants