| Announcement ID | MC805212 | Published Date | 06-25-2024 | |
| Service | General | Last Updated | 09-24-2024 | |
| Category | Plan for change | Expiration Date | 11-11-2024 | |
| Roadmap ID | Action Required by Date | |||
| Tags | Admin impact, New feature, User impact | |||
| Summary |
|---|
| The message details an improved resharing experience for Microsoft 365 apps, allowing view-only shared links to be copied directly from the Share dialog. Rollout begins mid-September 2024, with general availability by early October 2024. No admin action is required, but user notification is advised. |
| More Information |
|---|
Currently, when you share a link with view-only permissions in Microsoft 365 apps, clicking on Copy link defaults to an "Only people with existing access" link that does not always target your intended people. With this new feature, when you share a link with view-only permissions with other people, those people will now be able to copy that same link directly from the Share dialog when they attempt to share. If your only option to share with others is Only people with existing access, you will be able to send a request to the owner to share this file with specific people directly in the sharing control. The owner of the file will then receive a request and will be able to approve or reject the request. When this will happen:Targeted Release: We will begin rolling out mid-September (previously mid-August) 2024 and expect to complete by late September (previously late August) 2024. General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late September (previously mid-September) 2024 and expect to complete by early October 2024 (previously late-September). How this will affect your organization:With this new feature, anyone who accesses a Microsoft 365 apps file with view-only permissions will see this new experience. What you need to do to prepare:This rollout will happen automatically by the specified dates with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. |