Update applications-authenticationbehaviors.md

I spent a lot of time and even engaged engineering because I was using the application Client ID and the command was failing. some customers struggled to achieve  something simple as this because it is not clear what ID should be used

Author: rdiazel

concepts/applications-authenticationbehaviors.md

@@ -468,7 +468,7 @@ Content-Type: application/json
 
 By default, applications created after August 31, 2024 will receive a `403 Unauthorized` error when making requests to Azure AD Graph APIs, unless they're configured to allow extended Azure AD Graph access. Additionally, existing apps created before August 31, 2024 and making requests to Azure AD Graph APIs must be configured to allow extended Azure AD Graph access by February 1, 2025. This extended access is available only until June 30, 2025, when Azure AD Graph is fully retired. After this date, all apps will receive a `403 Unauthorized` error when making requests to Azure AD Graph APIs, regardless of their extended access configuration. For more information, see [June 2024 update on Azure AD Graph API retirement](https://techcommunity.microsoft.com/t5/microsoft-entra-blog/june-2024-update-on-azure-ad-graph-api-retirement/ba-p/4094534).
 
-The following request shows how to update an app to enable extended Azure AD Graph access. The request returns a `204 No Content` response code.
+The following request shows how to update an app to enable extended Azure AD Graph access. The ID used in this example is the Object ID of the application, not the Application ID. The request returns a `204 No Content` response code.
 
 #### Option 1