Microsoft 365 Error Codes

Fix Connect-PnPOnline 500 Errors in GCC SharePoint Online

Phi Hung VoPhi Hung Vo Nov 20, 2026 869 views

Question details

Resolve a 500 Internal Server Error when connecting to a GCC SharePoint tenant with Connect-PnPOnline and a custom client-side application.

Fix Connect-PnPOnline 500 Errors in GCC SharePoint Online
Product
SharePoint Online and PnP PowerShell
Device & OS
not provided
Scenario
A user connects to a GCC SharePoint tenant through a custom client-side application using Connect-PnPOnline.
Observed behavior
The GCC connection returns a 500 Internal Server Error, while connections to commercial tenants may continue to work.
Before you start

Note the affected tenant, connection time, and exact error message. Ask a Microsoft 365 administrator to check service health if you do not have access to the admin center.

Solution 1Recommended

Check SharePoint Online service health

Use the Microsoft 365 Service Health dashboard to determine whether a service incident is affecting PowerShell connections.

1
Open service health

Sign in to the Microsoft 365 admin center and go to Health > Service health.

2
Review SharePoint incidents

Select SharePoint Online and review active or recent incidents for connection failures involving PowerShell or custom client-side applications.

3
Retry after recovery

If an incident matches the symptoms, follow its status in the dashboard and retry Connect-PnPOnline after Microsoft reports that service is restored.

Check SharePoint Online service health
Historical incident references: Incident SP146217 described SharePoint Online PowerShell failures with a custom client-side application. A related incident, SP146251, was reported as resolved. Check the dashboard for the current status rather than assuming these incidents are still active.
Free Microsoft Office alternative

Work with Office files in WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move everyday document work. It does not fix SharePoint service incidents or Connect-PnPOnline errors.

Edit documents, spreadsheets, and presentations in a familiar interfaceOpen and save common Microsoft Office formats, including DOCX, XLSX, and PPTXUse a free, lightweight suite for everyday Office file work
microsoft office alternative - wps office

Frequently Asked Questions

Why does Connect-PnPOnline return a 500 error only in my GCC tenant?

A service issue may affect GCC connections while commercial tenants continue to work, but the error alone does not establish the cause. Check Health > Service health in the Microsoft 365 admin center for relevant SharePoint Online incidents.

Where can I check whether SharePoint Online is having an incident?

In the Microsoft 365 admin center, go to Health > Service health and select SharePoint Online. If you cannot access the dashboard, ask your Microsoft 365 administrator to check it.

Are incidents SP146217 and SP146251 still active?

These are historical incident references; SP146251 was reported as resolved. Review the Service health dashboard for current incidents and their status.

What should I include when reporting a persistent 500 error?

Include the affected GCC tenant or site, the error text, the time and time zone, and the Connect-PnPOnline command with credentials and tokens removed. Submit these details in a Microsoft 365 support request or a new support forum thread.

Can WPS Office fix a Connect-PnPOnline error?

No. WPS Office can help with Office documents, but SharePoint service and PnP PowerShell connection issues must be investigated through Microsoft service health or support.