Revert "AB#9108: [BULK] [Bundle-Security] - Scheduled execution to fix known issues (part 4)"

Author: JarrettRenshaw

support/azure/general/cannot-see-users-groups-list-iam.md

@@ -42,7 +42,7 @@ To resolve this issue, use one of the following methods:
 1. Run the [Update-MgUser](/powershell/module/microsoft.graph.users/update-mguser) cmdlet:
 
     ```powershell
-   Update-MgUser -UserId '00aa00aa-bb11-cc22-dd33-44ee44ee44ee' -UserType Member
+   Update-MgUser -UserId '0ba17ca9-0000-0000-0000-a5e34bc4803b' -UserType Member
     ```
     You can get the users Object ID by looking at the Users Profile page within the Azure portal.
 

support/azure/partner-solutions/ingestion-key-rotation-log-flow.md

@@ -27,7 +27,7 @@ The issue occurs because Azure isn't notified of the ingestion key rotation. The
 
 To work around the issue, manually update the ingestion key by using the following API call:
 
-1. Find the **Resource ID** of the Azure New Relic resource that's associated with the account to which the ingestion key was rotated. If multiple resources are linked to the same account, you can make the API call for any of them. The following is an example of a Resource ID: `/subscriptions/aaaabbbb-0000-cccc-1111-dddd2222eeee/resourceGroups/myRG/providers/NewRelic.Observability/monitors/MyNewRelicResource`.
+1. Find the **Resource ID** of the Azure New Relic resource that's associated with the account to which the ingestion key was rotated. If multiple resources are linked to the same account, you can make the API call for any of them. The following is an example of a Resource ID: `/subscriptions/0493ccca-0000-0000-0000-f9bca5fc5dc9/resourceGroups/myRG/providers/NewRelic.Observability/monitors/MyNewRelicResource`.
   It includes the subscription ID, the resource group name, and the Azure New Relic resource name.
 
 2. Make the API call to update the ingestion key. Use an API client to make a **POST** request to the following endpoint. You must replace the placeholders with your actual values:
@@ -37,7 +37,7 @@ To work around the issue, manually update the ingestion key by using the followi
      ```
      In this example, the full API endpoint is:
      ```HTTP
-     https://management.azure.com/subscriptions/aaaabbbb-0000-cccc-1111-dddd2222eeee/resourceGroups/myRG/providers/NewRelic.Observability/monitors/MyNewRelicResource/refreshIngestionKey
+     https://management.azure.com/subscriptions/0493ccca-0000-0000-0000-f9bca5fc5dc9/resourceGroups/myRG/providers/NewRelic.Observability/monitors/MyNewRelicResource/refreshIngestionKey
      ```
 
      **Query parameter**: `api-version`: `2024-10-01`

support/azure/virtual-machines/linux/troubleshoot-azure-fence-agent-rhel.md

@@ -154,8 +154,8 @@ If you check the */var/log/messages* log file, you'll see an output that resembl
 2020-04-06T10:06:51.045519+00:00 VM1 pacemaker-execd[29306]: notice: executing - rsc:rsc_st_azure action:start call_id:52
 2020-04-06T10:06:52.826702+00:00 VM1 /fence_azure_arm: Failed: AdalError: Get Token request returned http error: 400 and server response: {"error":"unauthorized_client","error_description":"AADSTS700016: Application with identifier '<application ID>'
 was not found in the directory '<directory name>'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant.
-You may have sent your authentication request to the wrong tenant.\r\nTrace ID: 0000aaaa-11bb-cccc-dd22-eeeeee333333\r\nCorrelation ID: aaaa0000-bb11-2222-33cc-444444dddddd\r\nTimestamp:2020-04-06 10:06:52Z","error_codes":[700016],"timestamp":"2020-04-06 10:06:52Z","trace_id":"0000aaaa-11bb-cccc-dd22-eeeeee333333",
-"correlation_id":"aaaa0000-bb11-2222-33cc-444444dddddd","error_uri":"https://login.microsoftonline.com/error?code=700016 "}
+You may have sent your authentication request to the wrong tenant.\r\nTrace ID: 9d86f824-52c1-45a8-b24f-c81473122d00\r\nCorrelation ID: 7dd6de5d-1d6a-4950-be8b-9a2cb2df8553\r\nTimestamp:2020-04-06 10:06:52Z","error_codes":[700016],"timestamp":"2020-04-06 10:06:52Z","trace_id":"9d86f824-52c1-45a8-b24f-c81473122d00",
+"correlation_id":"7dd6de5d-1d6a-4950-be8b-9a2cb2df8553","error_uri":"https://login.microsoftonline.com/error?code=700016 "}
 ```
 
 To troubleshoot the authentication failures, follow these steps:

support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md

@@ -30,7 +30,7 @@ Also, make sure the image has been properly prepared (generalized). * Instructio
 ```
 
 ```toutputext
-Deployment failed. Correlation ID: aaaa0000-bb11-2222-33cc-444444dddddd. {
+Deployment failed. Correlation ID: f9dcb33a-4e6e-45c5-9c9d-b29dd73da2e0. {
   "status": "Failed",
   "error": {
     "code": "ResourceDeploymentFailure",

support/azure/virtual-machines/windows/multiple-certificates-iaas-vm-extensions.md

@@ -32,14 +32,14 @@ In Windows, if you view the *C:\\WindowsAzure\\logs\\WaAppAgent.log* log file, y
 
 ```output
 [01/16/2017 21:42:25.50] [INFO]  Imported Certificate: DC=Windows Azure CRP Certificate Generator.
-[01/16/2017 21:42:25.50] [INFO]  Certificate thumbprint: AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00
-[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00 and hash AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00.
-[01/16/2017 21:42:25.50] [INFO]  Certificate AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00 is found.
-[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00 and hash BB22CC33DD44EE55FF66AA77BB88CC99DD00EE11.
+[01/16/2017 21:42:25.50] [INFO]  Certificate thumbprint: 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9
+[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9 and hash 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9.
+[01/16/2017 21:42:25.50] [INFO]  Certificate 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9 is found.
+[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9 and hash FC2FFCDEE6A8C6033EE4986B4D5080E3E2083CC9.
 ...
-[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00 and hash CC33DD44EE55FF66AA77BB88CC99DD00EE11FF22.
-[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00 and hash AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00.
-[01/16/2017 21:42:25.50] [INFO]  Certificate AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00 is found.
+[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9 and hash 1E1A0BF89A1FDD0722F4F94083A6CCDF94EFC78A.
+[01/16/2017 21:42:25.50] [INFO]  Comparing normalizedHash: 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9 and hash 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9.
+[01/16/2017 21:42:25.50] [INFO]  Certificate 1D59A4E7F60F6D978124ED7D3E177B0D6A6806C9 is found.
 [01/16/2017 21:42:25.50] [INFO]  Certificate with the subject: DC=Windows Azure CRP Certificate Generator will not be added because it already exists in the store.
 [01/16/2017 21:42:25.50] [INFO]  Successfully imported cert TenantEncryptionCert into the store My
 ```

support/azure/virtual-machines/windows/troubleshoot-extension-certificates-issues-windows-vm.md

@@ -68,15 +68,15 @@ The following list outlines the most common errors that might occur when you use
   ```output
   DiagnosticsPluginLauncher.exe Information: 0 : [6/29/2020 1:32:20 PM] Decrypting private configuration
   
-  DiagnosticsPluginLauncher.exe Warning: 0 : [6/29/2020 1:32:20 PM] No certficate with given thumbprint found in the certificate store. Thumbprint:AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00
+  DiagnosticsPluginLauncher.exe Warning: 0 : [6/29/2020 1:32:20 PM] No certficate with given thumbprint found in the certificate store. Thumbprint:34C8CDC747693E0E33A9648703E3990EC4F2C484
   
   DiagnosticsPluginLauncher.exe Information: 0 : [6/29/2020 1:32:20 PM] Retrying after 30 seconds. Retry attempt 1
   
-  DiagnosticsPluginLauncher.exe Warning: 0 : [6/29/2020 1:32:50 PM] No certficate with given thumbprint found in the certificate store. Thumbprint:AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00
+  DiagnosticsPluginLauncher.exe Warning: 0 : [6/29/2020 1:32:50 PM] No certficate with given thumbprint found in the certificate store. Thumbprint:34C8CDC747693E0E33A9648703E3990EC4F2C484
   
   DiagnosticsPluginLauncher.exe Information: 0 : [6/29/2020 1:32:50 PM] Retrying after 30 seconds. Retry attempt 2
   
-  DiagnosticsPluginLauncher.exe Warning: 0 : [6/29/2020 1:33:20 PM] No certficate with given thumbprint found in the certificate store. Thumbprint:AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00
+  DiagnosticsPluginLauncher.exe Warning: 0 : [6/29/2020 1:33:20 PM] No certficate with given thumbprint found in the certificate store. Thumbprint:34C8CDC747693E0E33A9648703E3990EC4F2C484
   
   DiagnosticsPluginLauncher.exe Information: 0 : [6/29/2020 1:33:20 PM] Retrying after 30 seconds. Retry attempt 3
   

support/developer/webapps/iis/www-administration-management/diagnosing-failures-with-remote-administration.md

@@ -98,7 +98,7 @@ Use `netsh` commands mentioned in the previous paragraph to determine if the bin
 1. Associate the cert with the port:  
 
     ```Console
-    netsh http add sslcert ipport=0.0.0.0:8172 certhash=<certHash> appid={00001111-aaaa-2222-bbbb-3333cccc4444}
+    netsh http add sslcert ipport=0.0.0.0:8172 certhash=<certHash> appid={d7d72267-fcf9-4424-9eec-7e1d8dcec9a9}
     ```
 
 ## Don't want to see the prompt on the client every time you connect to the remote server?

support/dynamics-365/customer-service/service-level-agreements/service-anchor-installation-fails-after-ol-migration.md

@@ -24,7 +24,7 @@ This issue occurs due to the active layer formed on the `Name` attribute of the
 
 To solve this issue, make an API call, as shown below, to remove the active layer on the `Name` attribute of the `slaitem` entity.
 
-`https://[orgURL]/api/data/v9.1/RemoveActiveCustomizations(SolutionComponentName='Attribute',ComponentId=aaaabbbb-0000-cccc-1111-dddd2222eeee)`
+`https://[orgURL]/api/data/v9.1/RemoveActiveCustomizations(SolutionComponentName='Attribute',ComponentId=6FE93FC3-E9FB-4298-A3FF-4D7EDF8BAFE8)`
 
 > [!NOTE]
 > Replace [orgURL] with the actual organization URL.

support/dynamics-365/finance/tax/cannot-set-dataverse-virtual-table-visibility.md

@@ -101,7 +101,7 @@ The 401 "Unauthorized" error occurs if the "Check connection" process for connec
 
 1. In the RCS environment, go to **Electronic reporting** \> **Connected applications** \> **Dataverse application record**.
 2. The **Application** field shows the URL of the database instance. Confirm that you can sign in to that Dataverse instance by using the same account that you use to sign in to the RCS environment.
-3. Confirm that the **Tenant** field is set to your account's tenant ID (for example, **aaaabbbb-0000-cccc-1111-dddd2222eeee**) or tenant URL (for example, `taxserviceint.onmicrosoft.com`).
+3. Confirm that the **Tenant** field is set to your account's tenant ID (for example, **d335a570-a05b-4bc5-8eb3-c42c65f9560d**) or tenant URL (for example, `taxserviceint.onmicrosoft.com`).
 4. Select **Check connection**. The process should be successful.
 
 > [!IMPORTANT]