diff --git a/en/docs/api-security/key-management/third-party-key-managers/configure-azure-ad-key-manager.md b/en/docs/api-security/key-management/third-party-key-managers/configure-azure-ad-key-manager.md index 06dc38c4f0..a24bb38bc2 100644 --- a/en/docs/api-security/key-management/third-party-key-managers/configure-azure-ad-key-manager.md +++ b/en/docs/api-security/key-management/third-party-key-managers/configure-azure-ad-key-manager.md @@ -193,6 +193,41 @@ Start the API Manager server and log-in to the Admin portal to configure Azure A + + !!! note "Handling Azure Application Synchronization Delays" + This capability is supported only from the U2 levels listed below in APIM products + + - wso2am-4.6.0 - U2 level 19 + - wso2am-acp-4.6.0 - U2 level 20 + - wso2am-universal-gw-4.6.0 - U2 level 19 + + Due to eventual consistency in Azure, there can be delays when creating Applications and Service Principals. + To mitigate issues caused by these synchronization delays, polling is performed for all Azure creation-related interactions. + The polling behavior can be configured using the Initial Delay and Maximum Waiting Time parameters, which are available in the Connector Configuration section. + These fields are described in the table below. + Backoff strategy: The delay between polling attempts is doubled after each retry, up to the given maximum delay. +
| Configuration | +Instruction | +Default Value | +
|---|---|---|
| Initial Delay (in ms) for Application Polling | +Provide an initial time to wait before starting polling for Azure Application creation | +500 ms | +
| Maximum Waiting Time (in ms) for Application Polling | +Provide the maximum time to wait for Azure Application creation | +5000 ms | +