Overview

Fix permission and scope issues blocking connector access.

Audience

• Admin
• Ops

Product Area

Connectors

Prerequisites

• Connector error present

Steps

1. Inspect permission error code

Read provider error code and map to missing scope/role.

1. Reauthorize connector

Apply corrected scopes and rerun connector validation.

Expected Result

The Connectors workflow completes without unresolved validation errors, and the result is visible to the intended roles.

Security and Audit Notes

• Use the least-privileged role that can complete the task.
• Confirm the resulting change or decision appears in the workspace audit trail when the workflow changes customer data or access.

Limits and Preconditions

• Available controls depend on the tenant plan, enabled modules, jurisdiction, and administrator policy.
• If a named control is not visible, confirm entitlement and role access before treating the behavior as a product failure.

Troubleshooting

• Token updated without scope change: Re-consent integration with expanded required scopes.

Related Articles

• Connect SharePoint
• Connect Google Drive

Escalation

If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.