Release 202605.0.0
Enhancement Requests
Shared Mailbox Support in M365 Trusted Sharing app: Users can now access and manage Trusted Shares involving Shared Mailboxes directly from within the Outlook section of the M365 app. This streamlines collaboration for teams that rely on shared mailboxes by eliminating the need to switch between applications. Members of shared mailboxes will see the shared mailbox under the Outlook share navigation tab. When a shared mailbox is selected, all Trusted Shares specific to that shared mailbox are shown.
Support for Login.Gov SAML SSO: Organizations can now authenticate users through Login.Gov as a SAML Single Sign-On identity provider. This expands secure access options for government-affiliated agencies and contractors, enabling seamless and compliant authentication aligned with federal identity standards.
Support for custom sharing request workflow link when sharing from a SharePoint site is not enabled: Within the Device Policy page of the Admin Conole, administrators can now configure a custom link that is presented to users within the blocked sharing message that is displayed to users when external sharing is not enabled for SharePoint site. This link allows users to initiate an approved workflow for requesting that Trusted Sharing be enabled for that site. This provides a guided way for users to request that external sharing be enabled, while allowing administrators to control the request process through their own preferred workflow.
Admin Management of Trusted Sharing via Trusted Sharing Action Menu and M365 Trusted Sharing App: Within the Azure AD User Groups section of the Admin Console, AD Groups can now be configured to limit Trusted Sharing to members of selected groups. A new self-service request workflow allows members outside of the configured AD Groups to request access Trusted Sharing rights when using the M365 Trusted Sharing app or when accessing ‘External Share’ from the Trusted Sharing Action Menu. This provides greater control over user onboarding while reducing administrative overhead. IT teams maintain full control through the approval process while users experience faster time-to-productivity.
Bugs
Share With Me Link (SWML) URL not defaulting to HTTPS: Resolved an issue where the SWML URL did not default or enforce a secure HTTPS connection, ensuring all portal traffic is encrypted by default.
Error on Cloud Providers page within Cloud Web Portal when accessing OneDrive files: Resolved an issue where a user encountered an error on the Cloud Providers page when attempting to browse additional files stored in OneDrive.
M365 Trusted Sharing App version update causing "Application Launch Error": Resolved an issue where updating to a newer M365 App version caused an "Application Launch Error," preventing users from opening the application.
"Missing User Registration" error for new M365 Trusted Sharing App users: Resolved an issue where newly onboarded users received a "Missing User Registration" error upon their first attempt to access the M365 App.
Audit event for "Add recipient" incorrectly showing Owner: Resolved an issue where the audit trail for adding a recipient incorrectly attributed the action to the Owner, even when a Co-Owner was the one who approved and added the recipient.
Trusted Share invites from Co-Owners sent from Owner email: Resolved an issue where Trusted Share invitations initiated by Co-Owners were incorrectly sent from the Owner's email address, causing confusion for recipients.
DLP Rule Sync failure due to duplicate GUIDs: Resolved an issue where Data Loss Prevention rule synchronization failed because standard Microsoft rules shared the same GUID, preventing policy enforcement.
Data Attributes configuration uploads overriding other organizations: Resolved an issue where uploading a new Data Attributes configuration inadvertently overwrote configuration files belonging to other organizations.
M365 Trusted Sharing App "Application Launch Error" in new tenants: Resolved an issue where the M365 App produced an "Application Launch Error" when launched in a newly provisioned tenant, blocking first-time setup.
Informational email notifications not delivered with sender's branding: Resolved an issue where informational email notifications were sent without the sender's configured branding, resulting in generic-looking communications.
Internal server error when rejecting extension requests: Resolved an issue where users received an internal server error when attempting to reject an extension request, preventing them from completing the action.