SPSiteManager API started returning an unexpected Status code

[kstat]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

No response

Describe the bug / error

GET request to /_api/SPSiteManager/status for a non-existent Site URL appears to now be returning a Status Code value of '1' (i.e., Provisioning) as opposed to expected Status Code value of '0' (i.e., Not Found), as per status code definitions here.

Note that this API call was correctly returning Status Code '0' until last week, and appears to have started returning a different response as of Friday 3/27.

Steps to reproduce

1. Establish a PnP PowerShell session with at-least Write access to the root site in tenant.
2. Invoke PnP PS cmdlet (or you can use any other method to invoke a GET request to SPO REST API)

Invoke-PnPSPRestMethod -Method Get -Url "https://tenant.sharepoint.com/_api/SPSiteManager/status?url='https://tenant.sharepoint.com/sites/doesnotexist'"

Expected behavior

Expected response is:

SiteId	SiteStatus	SiteUrl
	0

Received response is:

SiteId	SiteStatus	SiteUrl
	1

[Ashlesha-MSFT]

Hello @kstat,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

@kstat
We were able to reproduce the issue — the /SPSiteManager/status endpoint is returning SiteStatus = 1 for a non-existent site, whereas the documented behavior expects 0 (Not Found).

However, this appears to be a service/API behavior issue rather than a documentation problem. The correct place to raise this is the PnP PowerShell repository, where REST/API behavior issues are tracked:

https://github.com/pnp/powershell/issues

Therefore, this issue is not valid for this repository and should be reported there so the SharePoint Online engineering team can investigate.

[poi-radvine]

Same issue here, since yesterday all our site provisioning scipts are failing as the site check for deleted and active sites are returning a wrong status.

[amlehjakob]

Several critical business processes depend on this functionality and have been disrupted since Friday.

[Ashlesha-MSFT]

Thanks everyone for the additional reports and impact details — we’re able to reproduce this behavior as well.

We will check internally with the engineering team to confirm whether this can be resolved from their end. If confirmed, we’ll raise a bug for further investigation.

We’ll share an update here as soon as we have more information. Appreciate your patience.

[kstat]

@Ashlesha-MSFT @VesaJuvonen Any updates that could be shared on this one? Thank you!

[s-e-i-f1]

Great news! The problem is now fixed! 🎉

[poi-radvine]

Tested with our scripts and it works. Thank you or the Product Team for testing and implementing the working behavior.

[jansenbe]

We did fix this and things should work again as before. If you still encounter issues then please let us know.