Merge pull request #217247 from ChaitanyaNaykodi-MSFT/patch-136

prmerger-automator[bot] · web-flow · commit 38e93ada2756 · 2022-11-04T17:26:23.000Z
(AzureCXP) updated configurataion change time
diff --git a/articles/frontdoor/standard-premium/troubleshoot-compression.md b/articles/frontdoor/standard-premium/troubleshoot-compression.md
@@ -35,7 +35,7 @@ There are several possible causes, including:
 ## Troubleshooting steps
 
 > [!TIP]
-> As with deploying new endpoints, Azure Front Door configuration changes take some time to propagate through the network. Usually, changes are applied within 90 minutes.  If this is the first time you've set up compression for your CDN endpoint, you should consider waiting 1-2 hours to be sure the compression settings have propagated to the POPs. 
+> As with deploying new endpoints, Azure Front Door configuration changes take some time to propagate through the network. Usually, changes are applied within 10 minutes.  If this is the first time you've set up compression for your CDN endpoint, you should consider waiting 1-2 hours to be sure the compression settings have propagated to the POPs. 
 > 
 
 ### Verify the request

Original file line number	Diff line number	Diff line change
`@@ -35,7 +35,7 @@ There are several possible causes, including:`
`35`	`35`	`## Troubleshooting steps`
`36`	`36`
`37`	`37`	`> [!TIP]`
`38`		`-> As with deploying new endpoints, Azure Front Door configuration changes take some time to propagate through the network. Usually, changes are applied within 90 minutes. If this is the first time you've set up compression for your CDN endpoint, you should consider waiting 1-2 hours to be sure the compression settings have propagated to the POPs.`
	`38`	`+> As with deploying new endpoints, Azure Front Door configuration changes take some time to propagate through the network. Usually, changes are applied within 10 minutes. If this is the first time you've set up compression for your CDN endpoint, you should consider waiting 1-2 hours to be sure the compression settings have propagated to the POPs.`
`39`	`39`	`>`
`40`	`40`
`41`	`41`	`### Verify the request`