PendingActivation Adobe Acrobat Sign - Adobe Acrobat Sign

Hi @Shawn Utley,

Thank you for the update, and I appreciate you taking the time to contact Adobe and clarify the licensing situation, that information is very helpful.

Since you’ve now confirmed that the Adobe Acrobat Sign business version was not previously in place, the behavior you’re seeing makes more sense.

Regarding the “Configure Account” button now returning an “Oops - Error 500”, this typically indicates a server‑side or account‑provisioning issue rather than a problem with SharePoint itself. In most cases, this happens when the Adobe Acrobat Sign SaaS account is still being provisioned, updated, or synchronized on the Adobe side after a licensing change.

To help move this forward, here are a few things you can check or try:

1/ Allow some time after the license change

After enabling or upgrading to the Adobe Acrobat Sign business plan, it can take some time for Adobe’s backend systems to fully provision the account. During this period, the Configure Account button may fail with a 500 error.

2/ Retry with an admin account

Please make sure you’re signing in with an account that has the required permissions (Global Admin or SharePoint Admin in Microsoft 365, and appropriate admin rights in Adobe Acrobat Sign). If possible, try accessing the configuration again using an InPrivate/Incognito browser session to rule out cached credentials.

3/ Confirm the Adobe account status directly in Adobe Admin Console

Have your Adobe administrator verifies that:

• The Acrobat Sign business license is active
• The user attempting configuration is properly assigned
• The Acrobat Sign service is fully enabled for the tenant

4/ Contact Adobe Support again with the Error 500 details

If the error persists, the next step would be to follow up with Adobe Support and reference the Error 500 when configuring the Acrobat Sign SaaS account from SharePoint. Since the configuration endpoint and account provisioning are handled by Adobe, they are best positioned to check backend logs and complete or repair the activation.

At this stage, there’s nothing further to configure from the Microsoft or SharePoint side until Adobe confirms that the Acrobat Sign SaaS account is fully provisioned and healthy.

I hope this helps clarify what’s happening and what the most effective next steps are. Please feel free to share any updates from Adobe, and I’ll be happy to continue guiding you where possible.

I look forward to your reply.

Hi @Shawn Utley,

Thank you for your response.

To confirm whether Adobe Acrobat Sign was installed properly in SharePoint, there are a few concrete checks an administrator can perform. These steps help distinguish between an installation issue and a pending activation or licensing requirement.

1/ Check the SharePoint App Catalog:

• Go to the SharePoint Admin Center
• Navigate to More features > Apps > App Catalog
• Open the Apps for SharePoint section
• Locate Adobe Acrobat Sign – Adobe Acrobat Sign

If the app appears in the catalog and its status shows Enabled, Installed, or Deployed, that confirms the app package itself was installed successfully. If it still shows PendingActivation, it usually means the app is installed but waiting on admin approval or external activation (rather than being broken).

2/ Verify app permissions and approval:

• In the Microsoft 365 Admin Center, go to Settings > Integrated apps
• Find Adobe Acrobat Sign
• Confirm that all requested permissions have been reviewed and approved by a Global Admin or SharePoint Admin

If permissions are missing or not approved, the app can remain in a pending state even though it’s installed.

3/ Confirm it’s available at the site level:

• Go to the SharePoint site where you plan to use Acrobat Sign
• Select Site contents
• Check whether Adobe Acrobat Sign appears as an installed app

If it appears here, that’s another indication the installation itself completed successfully.

4/ When to consider reinstalling Reinstallation is usually only necessary if:

• The app does not appear in the App Catalog at all.
• Or the app is missing from Site contents even after deployment

If the app is visible but marked PendingActivation, reinstalling typically won’t resolve it, as this status is most often related to admin approval or Adobe‑side licensing and activation.

If the installation checks above look correct, the next things to confirm are:

• An active Adobe Acrobat Sign license is assigned
• Any required activation steps on the Adobe side have been completed

If those are already in place and the status doesn’t change, the recommended next step is to contact Adobe Support, since the final activation is managed by Adobe rather than Microsoft.

I hope this helps clarify how to tell whether the app is installed properly and what to check next. Please feel free to let me know what you see during these checks, and I’ll be happy to guide you further if possible.