Merge pull request #10649 from MicrosoftDocs/learn-build-service-prodbot/docutune-autopr-20260201-234916-8768968-ignore-build

AB#9643: [BULK] [Bundle-Security] - Scheduled execution to fix known issues (part 5)

Author: ryanberg-aquent

support/entra/entra-id/app-integration/error-code-AADSTS650056-misconfigured-app.md

@@ -89,7 +89,7 @@ For example:
 ```HTTP
 https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize
 ?response\_type=code
-&client\_id=044abcc4-914c-4444-9c3f-48cc3140b6b4
+&client\_id=00001111-aaaa-2222-bbbb-3333cccc4444
 &resource=https://vault.azure.net/
 &scope=openid
 &prompt=consent
@@ -111,7 +111,7 @@ For example:
 ```HTTP
 https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/v2.0/authorize
 ?response_type=code
-&client_id=044abcc4-914c-4444-9c3f-48cc3140b6b4
+&client_id=00001111-aaaa-2222-bbbb-3333cccc4444
 &scope=openid+https://vault.azure.net/user_impersonation
 &prompt=consent
 ```

support/entra/entra-id/app-integration/idx10501-token-signature-validation-error.md

@@ -50,7 +50,7 @@ For SAML, Microsoft Entra ID uses the app-specific certificate to sign tokens. T
 3. If your app uses custom signing keys that use a [claims-mapping policy](/entra/identity-platform/saml-claims-customization), you must append an `appid` query parameter that contains the app client ID. This step is necessary to retrieve a `jwks_uri` that points to the app’s specific signing key information. For example:
 
     ```http
-   https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration?appid=6731de76-14a6-49ae-97bc-6eba6914391e
+   https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration?appid=00001111-aaaa-2222-bbbb-3333cccc4444
     ```
     
 ### Middleware configuration examples

support/entra/entra-id/app-integration/send-notification-details.md

@@ -59,9 +59,9 @@ See the following descriptions for more details about the notifications.
 - **UPN** – the user who performed the operation
   - Example – **tperkins\@f128.info**
 - **Tenant ID** – the unique ID of the tenant that the user who performed the operation was a member of
-  - Example – **7918d4b5-0442-4a97-be2d-36f9f9962ece**
+  - Example – **aaaabbbb-0000-cccc-1111-dddd2222eeee**
 - **User object ID** – the unique ID of the user who performed the operation
-  - Example – **17f84be4-51f8-483a-b533-383791227a99**
+  - Example – **cccccccc-2222-3333-4444-dddddddddddd**
 
 ### Detailed Notification Items
 
@@ -75,6 +75,6 @@ See the following descriptions for more details about the notifications.
   - Example – **Internal url `https://bing.com/` is invalid since it is already in use**
 - **Copy error** – Select the **copy icon** to the right of the **Copy error** textbox to copy all the notification details to share with a support or product group engineer
   - Example
-    ```{"errorCode":"InternalUrl\_Duplicate","localizedErrorDetails":{"errorDetail":"Internal url 'https://google.com/' is invalid since it is already in use"},"operationResults":\[{"objectId":null,"displayName":null,"status":0,"details":"Internal url 'https://bing.com/' is invalid since it is already in use"}\],"timeStampUtc":"2017-03-23T19:50:26.465743Z","clientRequestId":"302fd775-3329-4670-a9f3-bea37004f0bb","internalTransactionId":"ea5b5475-03b9-4f08-8e95-bbb11289ab65","upn":"[email protected]","tenantId":"7918d4b5-0442-4a97-be2d-36f9f9962ece","userObjectId":"17f84be4-51f8-483a-b533-383791227a99"}```
+    ```{"errorCode":"InternalUrl\_Duplicate","localizedErrorDetails":{"errorDetail":"Internal url 'https://google.com/' is invalid since it is already in use"},"operationResults":\[{"objectId":null,"displayName":null,"status":0,"details":"Internal url 'https://bing.com/' is invalid since it is already in use"}\],"timeStampUtc":"2017-03-23T19:50:26.465743Z","clientRequestId":"aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb","internalTransactionId":"bbbbbbbb-1111-2222-3333-cccccccccccc","upn":"[email protected]","tenantId":"aaaabbbb-0000-cccc-1111-dddd2222eeee","userObjectId":"cccccccc-2222-3333-4444-dddddddddddd"}```
 
 

support/entra/entra-id/app-integration/troubleshoot-consent-issues.md

@@ -74,7 +74,7 @@ The following table provides an example of the parameters used in a sign-in requ
 |---|---|---|
 |Aad-Instance|    `<Aad-Instance>`|    login.microsoftonline.com|
 |Tenant-ID|    `<Tenant-ID>` portion of the sign-in request|    common|
-|App-ID|    `<App-ID>` portion of the sign-in request|    1f92960d-1442-4cd2-8c76-d13c5dcb30bf|
+|App-ID|    `<App-ID>` portion of the sign-in request|    00001111-aaaa-2222-bbbb-3333cccc4444|
 |Scope|    `<Scope>` portion of the sign-in request|    Openid+User.Read+Directory.Read.All|
 |App-URI-ID|    V1 endpoint: `<App-URI-ID>` portion of the sign-in request</br>   </br>V2 endpoint: For resources other than Microsoft Graph, this will be the portion before the scope name. For example, for `https://analysis.windows.net/powerbi/api/App.Read.All`, `App.Read.All` is the scope name, so the `App-URI-ID` is `https://analysis.windows.net/powerbi/api`.|    https://graph.microsoft.com|
 |Prompt|    `<Prompt>` portion of the sign-in request     ||
@@ -166,11 +166,11 @@ Sometimes, signing in to the application requires passing the `prompt` parameter
 
 Your sign-in request might look like this:
 
-`https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize?client_id=1f92960d-1442-4cd2-8c76-d13c5dcb30bf&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile+User.Read+Directory.Read.All&prompt=consent`
+`https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize?client_id=00001111-aaaa-2222-bbbb-3333cccc4444&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile+User.Read+Directory.Read.All&prompt=consent`
 
 So, to resolve consent issues, remove the `prompt` parameter as follows:
 
-`https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize?client_id=1f92960d-1442-4cd2-8c76-d13c5dcb30bf&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile+User.Read+Directory.Read.All`
+`https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize?client_id=00001111-aaaa-2222-bbbb-3333cccc4444&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile+User.Read+Directory.Read.All`
 
 ## Perform admin consent
 
@@ -186,11 +186,11 @@ To resolve consent issues, perform admin consent by following these steps:
 
 3. If the administrator doesn't get the consent screen, grab the sign-in address, add `&prompt=consent` to the end, and then use this request to perform admin consent.
 
-    Here's an example: `https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize?client_id=1f92960d-1442-4cd2-8c76-d13c5dcb30bf&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile&tresource=https://graph.microsoft.com&prompt=consent`
+    Here's an example: `https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize?client_id=00001111-aaaa-2222-bbbb-3333cccc4444&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile&tresource=https://graph.microsoft.com&prompt=consent`
 
     If the requested permissions aren't listed in the application registration, use the Microsoft identity platform (V2) endpoint to force admin consent. V2 endpoint requires each permission scope to be passed in the `scope` parameter as follows:
 
-    `https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/v2.0/authorize?client_id=1f92960d-1442-4cd2-8c76-d13c5dcb30bf&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile+User.Read+Directory.Read.All&prompt=consent`
+    `https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/v2.0/authorize?client_id=00001111-aaaa-2222-bbbb-3333cccc4444&response_type=code&redirect_uri=https://www.contoso.com&scope=openid+profile+User.Read+Directory.Read.All&prompt=consent`
 
 > [!NOTE]
 > - Permission scopes used by the application must be provided by the application owner.
@@ -239,4 +239,4 @@ You can use the Microsoft Entra activity logs to get more details. To do so, fol
 
 In certain scenarios, you're required to perform admin consent even though you might allow users to consent and the permission normally doesn't require an admin to consent. For example, when the status reason shows "Microsoft.Online.Security.UserConsentBlockedForRiskyAppsException." For more information, see [Unexpected error when performing consent to an application](/entra/identity/enterprise-apps/application-sign-in-unexpected-user-consent-error#requesting-not-authorized-permissions-error) and [Unexpected consent prompt when signing in to an application](/entra/identity/enterprise-apps/application-sign-in-unexpected-user-consent-prompt).
 
- 
+ 

support/entra/entra-id/app-integration/troubleshoot-cross-origin-resource-sharing-issues.md

@@ -196,7 +196,7 @@ function MSALInstanceFactory(): IPublicClientApplication {
   return new PublicClientApplication({
     auth: {
       authority: 'https://contoso.b2clogin.com/tfp/655e51e9-be5e-xxxx-xxxx-38aa6558xxxx/b2c_1_susi/v2.0/',
-      clientId: 'fb2ad7b7-2032-4a66-8723-e993eb4b9004',
+      clientId: '00001111-aaaa-2222-bbbb-3333cccc4444',
       redirectUri: 'http://localhost:4200',
       knownAuthorities: ['contoso.b2clogin.com'],
       protocolMode: ProtocolMode.OIDC

support/entra/entra-id/app-integration/troubleshoot-error-idx10501-aspnet-b2c.md

@@ -91,7 +91,7 @@ Example of `Appsettings.json`
 {
   "AzureADB2C": {
     "Instance": "https://markstestorganization1.b2clogin.com",
-    "ClientId": "09717d12-ca7f-4388-8393-dafe42c0c3a5",
+    "ClientId": "00001111-aaaa-2222-bbbb-3333cccc4444",
     "CallbackPath": "/signin-oidc",
     "SignedOutCallbackPath": "/signout/B2C_1_signupsignin1",
     "Domain": "markstestorganization1.onmicrosoft.com",
@@ -101,7 +101,7 @@ Example of `Appsettings.json`
   },
   "AzureADB2CEditEmail": {
     "Instance": "https://markstestorganization1.b2clogin.com",
-    "ClientId": "09717d12-ca7f-4388-8393-dafe42c0c3a5",
+    "ClientId": "00001111-aaaa-2222-bbbb-3333cccc4444",
     "CallbackPath": "/signin-oidc-editemail",
     "SignedOutCallbackPath": "/signout/B2C_1_signupsignin1",
     "Domain": "markstestorganization1.onmicrosoft.com",

support/entra/entra-id/dir-dmns-obj/troubleshoot-user-creation-deletion-issues.md

@@ -142,7 +142,7 @@ DELETE https://graph.microsoft.com/v1.0/users/[email protected]
 To delete a user in Azure PowerShell, run the [Remove-MgUser](/powershell/module/microsoft.graph.users/remove-mguser?view=graph-powershell-1.0&preserve-view=true) cmdlet. To run this command, you must connect to Microsoft Graph with at least the `User.DeleteRestore.All` permission.
 
 ```powershell
-Remove-MgUser -UserId '5c442efb-5e66-484a-936a-91b6810bed14'
+Remove-MgUser -UserId '00aa00aa-bb11-cc22-dd33-44ee44ee44ee'
 ```
 
 ## [Azure CLI](#tab/azure-cli)