I am encountering the following error since yesterday for all our process that use
UiPathTeam.Sharepoint.Activities v1.7.0 with Windows-Legacy.
Sharepoint application scope: Cannot contact web site ‘https://{mySpSite}’ or the web site does not support SharePoint Online credentials. The response status code is ‘Forbidden’. The response headers are ‘X-NetworkStatistics=0,64229,0,0,5171882,939428,939428,19356, X-SharePointHealthScore=2, X-Forms_Based_Auth_Required=https:/{mySpSite} Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically., SPRequestGuid=7d3408a2-40b2-9000-88e6-410dd690ab4b, request-id=7d3408a2-40b2-9000-88e6-410dd690ab4b, MS-CV=ogg0fbJAAJCI5kEN1pCrSw.0, Strict-Transport-Security=max-age=31536000, IsOCDI=0, SPRequestDuration=13, SPIisLatency=0, MicrosoftSharePointTeamServices=16.0.0.27125, X-Content-Type-Options=nosniff, X-MS-InvokeApp=1; RequireReadOnly, X-Cache=CONFIG_NOCACHE, X-MSEdge-Ref=Ref A: 6A541DB7EAB0427EBE0E1E2D0DC2AAFC Ref B: FRA261110502036 Ref C: 2026-04-09T07:18:08Z, Content-Length=13, Content-Type=text/plain; charset=utf-8, Date=Thu, 09 Apr 2026 07:18:08 GMT, P3P=CP=“ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI”, X-Powered-By=ASP.NET’.
Funny enought, same login type and activities work on Windows with
UiPathTeam.SharePoint.Activities v2.0.3 or v2.0.2
It looks much more like your legacy package/authentication path has started failing because Microsoft is retiring legacy SharePoint Online authentication
Treat 1.7.0 on Windows-Legacy as no longer safe for SharePoint Online.
Move those automations to UiPathTeam.SharePoint.Activities 2.0.3 on Windows projects if possible. Marketplace explicitly positions 2.0.0+ as the migration path from the old legacy package.
I had indeed migrated a process to Windows and everything works regarding authentication. One more question. We are using the configuration PlatformType Online with Login Mode - Online - with username and password. Is this type in danger as 1st of may? or because I have new Activities with Windows they somehow solve what microsoft is blocking?