logo
search
Copilot Access Problems

Fix Copilot Studio Connector Sign-In Failed: Create First-Party Connection Error

Adam DavisAdam Davis Sep 27, 2026 869 views

Question details

Users encounter an authentication failure when trying to create a first-party connection for specific connectors in Copilot Studio.

How to Fix Copilot Studio Connector Sign-In 'Create First-Party Connection Failed' Error
Product
Microsoft Copilot Studio
Device & OS
not provided
Scenario
Setting up and authenticating a connector (such as Convert Word Document to PDF) within a Copilot Studio workflow.
Observed behavior
The system throws a 'Create First-Party Connection Failed' error during sign-in, even if other connectors in the same environment authenticate successfully.
Before you start

Ensure you have an active internet connection and that your Microsoft 365 account has administrative permissions to create new connections within your Power Platform environment.

Solution 1Recommended

Verify Environment Permissions and Reset Browser Session

This solution resolves temporary token glitches and ensures your account has the correct prerequisites to create connections in your region.

Connection creation failures are frequently caused by expired browser session tokens or a mismatch in environment permissions and regional availability.

1
Check Environment Permissions

Navigate to your Power Platform admin center and confirm that your user account is assigned the necessary security roles (like Environment Maker) to create connections in the current environment.

2
Verify Connector Regional Availability

Check the Microsoft documentation to ensure the specific connector (e.g., Convert Word Document to PDF) is supported and available in your environment's geographic region.

3
Sign Out Completely

Click on your profile picture in the top right corner of Copilot Studio and select 'Sign out' to clear your current session credentials.

4
Retry in a New Session

Open a new Private or Incognito browser window, navigate back to Copilot Studio, sign in with your credentials, and attempt to create the connector again.

Verify Environment Permissions and Reset Browser Session
Browser Cache: Using a Private/Incognito window ensures that no corrupted cached data or conflicting accounts interfere with the new authentication request.
Free Microsoft Office alternative

Easily Convert Word to PDF Offline with WPS Office

Tired of dealing with complex cloud connectors, authentication errors, and permissions just to convert a document? WPS Office provides a built-in, one-click Word to PDF conversion feature without relying on external cloud setups like Copilot Studio.

  1. 1. Open Your Document: Launch WPS Office and open the Word document (.docx) you want to convert.
  2. 2. Access the Export Feature: Click on the 'Menu' button in the top left corner, hover over 'Export to PDF', and select it.
  3. 3. Save as PDF: Adjust your export settings if necessary, then click 'Export to PDF' to instantly save your file locally without any cloud connector errors.
Built-in Word to PDF converter with no complex setup or authentication requiredFully compatible with Microsoft Office formats including .docx, .xlsx, and .pptxLightweight, fast, and works seamlessly offlineFree to use with a familiar, user-friendly interface that requires zero learning curve
microsoft office alternative - wps office

Frequently Asked Questions

Why does Copilot Studio show a 'Create First-Party Connection Failed' error?

This error typically occurs due to expired browser session tokens, insufficient user permissions in the Power Platform environment, or attempting to use a connector that is not supported in your specific region.

Can I use the 'Convert Word Document to PDF' connector in all regions?

Not necessarily. Some connectors have regional restrictions or are rolled out progressively. You should verify in the Microsoft Power Platform documentation that the connector is available for your tenant's region.

How do I find the correlation ID for a Copilot Studio error?

When the error message pops up, look for a 'View details' or 'More information' link. Clicking this will display the correlation ID, which is a unique string of characters that Microsoft support uses to track and diagnose your specific error event.

Will clearing my browser cache fix the connection sign-in issue?

Yes, clearing your browser cache or using an Incognito/Private browsing window forces Copilot Studio to generate a fresh authentication token, which often resolves unexpected sign-in failures.