Microsoft SharePoint eSignature: Adobe Acrobat Sign and Docusign integration will roll out globally
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 421194
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredBefore this rollout, the use of third-party providers as part of the Microsoft SharePoint eSignature pay-as-you-go platform is limited to regions supported by the native Microsoft SharePoint eSignature.
With this rollout, customers across the globe will be able to use third-party providers, wherever they are supported. Users will no longer be required to enable native SharePoint eSignature as a prerequisite for enabling either Docusign or Adobe Acrobat Sign. Pay-as-you-go must be set up to enable SharePoint eSignature, but Microsoft will not charge customers for using third-party providers.
This message is associated with Microsoft 365 Roadmap ID 421194.
When this will happen
General Availability (Worldwide): We will begin rolling out early November 2024 and expect to complete by mid-November 2024.
How this will affect your organization
After this rollout, admins can enable a third-party provider without enabling native SharePoint eSignature, and vice versa.
Microsoft 365 users who have licenses with Adobe Acrobat Sign or Docusign will be able to initiate eSignature requests with these providers from SharePoint.
What you need to do to prepare
Admins need to enable the feature in the Microsoft admin center at Setup > Automate content with Syntex> Go to Syntex > eSignature
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Learn more
Links from the notice and their documentation checksRelated public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.