MC792499: Add-in device permission prompt for camera, microphone, and geolocation on Edge and Chrome

Announcement IDMC792499Published Date05-13-2024
ServiceofficeonlineLast Updated05-16-2024
CategoryPlan for changeExpiration Date08-06-2024
Roadmap IDAction Required by Date
TagsAdmin impact, New feature, User impact


Summary
                Starting May 16, 2024, Microsoft will require add-in developers to prompt users for device permissions on Edge and Chrome for the web versions of Word, Excel, PowerPoint, and Outlook. A Device Permission API will be available to facilitate this change. No admin action is required before the rollout.


More Information

As of May 16, 2024, Microsoft requires add-in developers to prompt users for camera, microphone, and geolocation permission in these Microsoft Office applications:

  • Web versions of Microsoft Word, Excel, PowerPoint, and Outlook on Chromium-based browsers (such as Microsoft Edge or Google Chrome).
  • New Outlook for Windows

Add-ins that run on Office on Windows, Mac, or Safari already have prompts in place.

To allow add-in developers to prompt their users, we are releasing a Device Permission API.

When this will happen:

General Availability (Worldwide, GCC, GCC High, DoD): This API will be available on May 16, 2024.

How this will affect your organization:

For developers: If your organization is building add-ins for these affected Office applications and your add-in requires permission for microphone, camera, or geolocation, your developers must implement the new API to add the new prompt for the add-in to work. If your Outlook add-in uses event-based activation, browser permissions aren't inherited and prompting for permission isn't supported or recommended.

For users: Users may see extra prompts if they are using certain add-ins that run on these affected Office applications.

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your developers and users about this change and update any relevant documentation as appropriate.

Previous Post Next Post