Further explain the impact of using custom signing key

MarcialRosales · MarcialRosales · commit 672acfc5c0b1 · 2023-04-24T15:43:15.000+02:00
diff --git a/use-cases/azure.md b/use-cases/azure.md
@@ -126,7 +126,9 @@ Choose a role (only a single role can be selected at a time), click on the **Sel
 
 You do not need to create a custom signing key for your application. If you create one though, you must append an `appid` query parameter containing the *app ID* to the  `jwks_uri`.
 
-For example `https://login.microsoftonline.com/{tenant}/.well-known/openid-configuration?appid=<my-app-id>` contains a `jwks_uri` of  `https://login.microsoftonline.com/{tenant}/discovery/keys?appid=<my-app-id>`.
+For example, if you try `https://login.microsoftonline.com/{tenant}/.well-known/openid-configuration?appid=<my-app-id>` it returns a `jwks_uri` with the value  `https://login.microsoftonline.com/{tenant}/discovery/keys?appid=<my-app-id>`.
+
+If you do not use the above `jwks_uri`, the standard jwks_uri will not return your custom signing key and RabbitMQ will not be able to find the signing key to validate the token's signature.
 
 ## Configure RabbitMQ to use Azure AD as OAuth 2.0 authentication backend
 
