This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 88%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hi Microsoft team and community!
I would like to know if it's possible to change the Provisioning interval which is currently fixed for 40 minutes? And if yes, how to go about it? Thanks!
For context, I created an Encryption service on Azure, created a SAML app, enabled SSO and when provisioning, would like to speed up the provisioning cycle from 40 minutes to 5 to test for difference in user experience.
Would love a bit more info on if this is possible and if not, why not?
Thank you so much! Have an amazing day!
Hugo
Additional Microsoft Entra services and features related to identity, access, and network security
Answer accepted by question author
No, this is a fixed time and cannot be changed. Ran into this before and this was the answer provided by Microsoft Support. If you look carefully in the provisioning blade it also mentions this number is ‘fixed’.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 88%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESH%3C/text%3E%3C/svg%3E)
I wonder if they will ever change that config in the provisioning feature to give us admins flexibility in timing. Honestly, we have at least one application that I would really prefer it only run once or maybe twice per day, preferably at a specific time. The constant 40 min interval is overkill activity in that case. Our environment wouldn't need and shorter intervals that 40 minutes for anything.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 94%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
Hey, i just wrote a small article on how to bypass this
https://medium.com/@nadav.shaham_94592/how-we-bypassed-microsoft-ad-provisioning-interval-ff03d17477ce
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 1%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
We encountered this too, built Ploy to handle all of this and integrate directly with the apps. https://joinploy.com/