Repository navigation
SPSiteManager API Endpoint not creating requested site #10128
Description
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint REST API
Developer environment
None
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
Power Automate workflow
Describe the bug / error
We are maintaining a Power Automate workflow for creating a new SharePoint site. We recently had a scenario where a request was submitted for the creation of a SharePoint site, and the SPSiteManager/Create endpoint (https://tenantname.sharepoint.com/_api/SPSiteManager/Create) returned a success response. However, the site was not created. See below for the request body and response
Request Body:
{ "request": { "Title": "Post Luxembourg-Wallix Assessment", "Url": "https://tenantname.sharepoint.com/sites/Post Luxembourg-Wallix Assessment", "Description": "Site used to work collaboratively and store all documents, deliverables related to the assessment", "Owner": "Owner's email address", "Lcid": 1033, "WebTemplate": "STS#3", "SiteDesignId": "53e46c84-923a-406f-86ff-1fdc9dc67ae4", "ShareByEmailEnabled": true } }
Response Body:
{ "d": { "Create": { "__metadata": { "type": "Microsoft.SharePoint.Portal.SPSiteCreationResponse" }, "SiteId": "", "SiteStatus": 3, "SiteUrl": "" } } }
Steps to reproduce
Expected behavior
Create site with SiteStatus code value of '2'
Activity
Ashlesha-MSFT commentedon Feb 25, 2025
Hello ogeam,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
Ashlesha-MSFT commentedon Feb 25, 2025
ogeam ,
We are currently unable to reproduce the issue when attempting to create a POST action in the workflow using the following endpoint:
** https://tenantname.sharepoint.com/_api/SPSiteManager/Create.**
It appears that the URL is not valid. We have also tried replacing the tenantname placeholder with the actual tenant name, but we still encountered the same issue. Could you please assist us with the correct steps or provide further guidance to reproduce the problem?
ogeam commentedon Feb 26, 2025
Thanks for getting back. Yes, I substituted our tenant name for "tenantname" in the SharePoint URL for privacy reasons.
Is there any way I can share the flow ID with you privately?
ChetanSharma-msft commentedon Mar 4, 2025
Hello ogeam - Please share the details on these mail id's for v-ashlpawar@microsoft.com, v-chetsharma@microsoft.com.
ogeam commentedon Apr 11, 2025
Thank you, ChetanSharma-MSFT (@ChetanSharma-msft) ! I have just sent you a private email as requested.
Ashlesha-MSFT commentedon Aug 11, 2025
ogeam,
I wanted to let you know that we've escalated your reported issue to the engineering team for further investigation and resolution. They are currently looking into it, and we will provide updates as soon as they have more information.
Could you please check on your end and confirm whether the issue is still occurring?
ogeam commentedon Aug 11, 2025
Thanks for letting me know.
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.