Forum Discussion
Maximum rate of provisioing Sharepoint sites
We have a scenario where a Azure based webjob is using Grpah API to create large number of Sharepoint online sites . What is the limit on the rate of provisioning Sharepoint online sites ? Where is such imformation published? How can such limits be relaxed for a deployment phase of the project that requires such large number of sharepoint online sites to be created ?
Lalit Mohan I believe the API limits are not available publicly.
Regarding PnP provisioning (I think this was the second part of you reply, apologies if not), you can use this as a starting point:
I have worked in some projects with similar challenges and there is generally some work that can be done in advance to minimize the load on the APIs when the bulk of the work needs to take place.
For example, create blank sites in advance, provision blank lists/libraries, provision some custom fields/content types, etc...
Lalit Mohan there are no specific numbers on this as it depends on many things, like if you are provisioning a complex site or not.
If you are using PnP provisioning, then you are already covered by the build-in exponential back-off approach (recommended by Microsoft) to wait if you reach the throttling limits, but if not, you may need to implement that approach yourself.
In short, there is no way to fully bypass the API limits as they are there to ensure performance is not compromised. But there are a few things that can be done, like using different user accounts as throttling will first be applied at the user account level.
Planning will be key 🙂 And if possible, start earlier, just in case 🙂
- Lalit MohanMicrosoftthanks Jeol, what are the API limit numbers ? Also can point to more detailed documentation on this. thanks in advance. Regards
Lalit Mohan I believe the API limits are not available publicly.
Regarding PnP provisioning (I think this was the second part of you reply, apologies if not), you can use this as a starting point:
I have worked in some projects with similar challenges and there is generally some work that can be done in advance to minimize the load on the APIs when the bulk of the work needs to take place.
For example, create blank sites in advance, provision blank lists/libraries, provision some custom fields/content types, etc...