diff --git a/assets/js/search-data.json b/assets/js/search-data.json
index 6ae8dd6e..1374fc55 100644
--- a/assets/js/search-data.json
+++ b/assets/js/search-data.json
@@ -3949,7 +3949,7 @@
   },"564": {
     "doc": "System for Cross-domain Identity Management (SCIM)",
     "title": "Setting Up SCIM Provisioning in Entra ID (a.k.a Azure AD)",
-    "content": "Note: This guide assumes you’ve already set up an Entra ID enterprise application for federated authentication to lakeFS Cloud. In the Entra ID admin dashboard, go to Enterprise Applications and choose the lakeFS Cloud enterprise application from the list. Then click Provisioning in the sidebar and then Get Started. | In the provisioning settings set mode to Automatic | In Tenant URL enter the URL from the lakeFS Cloud provisioning settings | In Secret Token paste the token you copied in the previous step. If you haven’t created a token yet, you may do so now | Click Test Connection | If the test fails, please ensure you’ve entered the correct SCIM endpoint URL from lakeFS Cloud and copied the token correctly. Otherwise, click “Save” at the top of the settings panel | . Note: lakeFS Cloud is designed to work with the default attribute mapping for users and groups provided by Entra ID. If your organization has customized the user and/or group entities in Entra ID, you might want to set mappings in accordance with those. You can find details of how this is done in the Entra ID documentation. Incorrectly modifying these mappings can break provisioning functionality, so it’s advised to do so cautiously and only when necessary. ",
+    "content": "Note: This guide assumes you’ve already set up an Entra ID enterprise application for federated authentication to lakeFS Cloud. In the Entra ID admin dashboard, go to Enterprise Applications and choose the lakeFS Cloud enterprise application from the list. Then click Provisioning in the sidebar and then Get Started. | In the provisioning settings set mode to Automatic | In Tenant URL enter the URL from the lakeFS Cloud provisioning settings. You will need to append ?aadOptscim062020 to the end of the URL to ensure proper integration with Entra ID. | In Secret Token paste the token you copied in the previous step. If you haven’t created a token yet, you may do so now | Click Test Connection | If the test fails, please ensure you’ve entered the correct SCIM endpoint URL from lakeFS Cloud and copied the token correctly. Otherwise, click “Save” at the top of the settings panel | . Note: lakeFS Cloud is designed to work with the default attribute mapping for users and groups provided by Entra ID. If your organization has customized the user and/or group entities in Entra ID, you might want to set mappings in accordance with those. You can find details of how this is done in the Entra ID documentation. Incorrectly modifying these mappings can break provisioning functionality, so it’s advised to do so cautiously and only when necessary. ",
     "url": "/howto/scim.html#setting-up-scim-provisioning-in-entra-id-aka-azure-ad",
     
     "relUrl": "/howto/scim.html#setting-up-scim-provisioning-in-entra-id-aka-azure-ad"
diff --git a/howto/scim.html b/howto/scim.html
index f262e46b..f771b819 100644
--- a/howto/scim.html
+++ b/howto/scim.html
@@ -702,7 +702,7 @@ <h2 id="setting-up-scim-provisioning-in-entra-id-aka-azure-ad">
 
 <ol>
   <li>In the provisioning settings set mode to <strong>Automatic</strong></li>
-  <li>In <strong>Tenant URL</strong> enter the URL from the lakeFS Cloud provisioning settings</li>
+  <li>In <strong>Tenant URL</strong> enter the URL from the lakeFS Cloud provisioning settings. You will need to append <code class="language-plaintext highlighter-rouge">?aadOptscim062020</code> to the end of the URL to ensure proper integration with Entra ID.</li>
   <li>In <strong>Secret Token</strong> paste the token you copied in the previous step. If you haven’t created a token yet, you may do so now</li>
   <li>Click <strong>Test Connection</strong></li>
   <li>If the test fails, please ensure you’ve entered the correct SCIM endpoint URL from lakeFS Cloud and copied the token correctly. Otherwise, click “Save” at the top of the settings panel</li>