Merge pull request #203511 from owinoakelo/patch-11

Update application-provisioning-quarantine-status.md

Author: PRMerger-2

articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md

@@ -69,6 +69,20 @@ A job can go into quarantine regardless of failure counts for issues such as adm
 - A job with 20,000 failures and 100,000 success wouldn't go into quarantine because it does not exceed the 40% failure threshold or the 40,000 failure max.  
 - There's an absolute threshold of 60,000 failures that accounts for both reference and non-reference failures. For example, 40,000 users failed to be provisioned and 21,000 manager updates failed. The total is 61,000 failures and exceeds the 60,000 limit.
 
+**Retry duration**
+
+The logic documented here may be different for certain connectors to ensure best customer experience, but we generally have the below retry cycles after a failure:
+
+After the first failure, the first retry happens within the next 2 hours (usually in the next sync cycle).
+- The second retry happens 6 hours after the first failure.
+- The third retry happens 12 hours after the first failure.
+- The fourth retry happens 24 hours after the first failure.
+- The fifth retry happens 48 hours after the first failure.
+- The sixth retry happens 96 hours after the first failure
+- The seventh retry happens 168 hours after the first failure.
+
+After the 7th failure, entry is flagged and no further retries are run.
+
 
 ## How do I get my application out of quarantine?