Merge pull request #10345 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-10 18:00 UTC

Author: learn-build-service-prod[bot]

support/azure/virtual-machines/windows/serial-console-overview.md

@@ -32,13 +32,16 @@ Serial Console is available for virtual machines and virtual machine scale sets
 - Australia Central 2
 - Australia East
 - Australia Southeast
+- Austria East
+- Belgium Central
 - Brazil South
 - Brazil Southeast
 - Canada Central
 - Canada East
 - Central India
 - Central US
 - Central US EUAP
+- Chile Central
 - China East 2
 - China East 3
 - China North 2
@@ -50,12 +53,15 @@ Serial Console is available for virtual machines and virtual machine scale sets
 - France South
 - Germany North
 - Germany West Central
+- Indonesia Central
 - Israel Central
+- Israel Northwest
 - Italy North
 - Japan East
 - Japan West
 - Korea Central
 - Korea South
+- Malaysia West
 - Mexico Central
 - New Zealand North
 - North Central US

support/dynamics/gp/this-document-has-been-posted.md

@@ -55,16 +55,16 @@ To resolve this problem, use an SQL query tool to discover why the document is d
 5. Run the following script against the company database:
 
     ```sql
-    Select PSTGSTUS, BCHSOURC, VOIDSTTS,TRXSORCE, DEX_ROW_ID * from SOP10100 where SOPNUMBE = 'Enter your SOP Document number with issue'
+    Select PSTGSTUS, BCHSOURC, VOIDSTTS,TRXSORCE, DEX_ROW_ID, * from SOP10100 where SOPNUMBE = 'Enter your SOP Document number with issue'
     ```
 
 6. > [!NOTE]
    > The Dex_Row_ID value.
 7. Check values in the following columns for the SOP Document. If any of these values are incorrect, the document may appear as posted.
 
-    PSTGSTUS (For an unposted document, it should read "0.")  
-    BCHSOURC (For an unposted document, it should read "Sales Entry.")  
-    VOIDSTTS (For an unposted document, it should read "0.")  
+    PSTGSTUS (For an unposted document, it should read "0".)  
+    BCHSOURC (For an unposted document, it should read "Sales Entry".)  
+    VOIDSTTS (For an unposted document, it should read "0".)  
     TRXSORCE (For an unposted document, it should be blank.)
 8. Run the following scripts against the company database to correct any of the four values from step 6:
 

support/mem/configmgr/cloud-services/public-ip-creation-error.md

@@ -75,9 +75,7 @@ Current Configuration Manager releases don't specify Availability Zone when crea
 
 ## Resolution
 
-At this point, there's no confirmed impact from this behavior, so we recommend that you ignore these errors.
-
-Microsoft plans to resolve this problem in a future release of Microsoft Configuration Manager.
+Microsoft has released a hotfix to address this issue: [Cloud management gateway deployment maintenance update for Configuration Manager 2409, 2503](/intune/configmgr/hotfix/2503/35958849). [Configuration Manager 2509](/intune/configmgr/hotfix/2509/35877153) includes this hotfix.
 
 ## More information
 

support/mem/configmgr/setup-migrate-backup-recovery/understand-troubleshoot-updates-servicing.md

@@ -86,7 +86,7 @@ For reference, the following table lists well-known update package GUIDs. The li
 | Configuration Manager 2403 HFRU | A02D38C5-021E-4144-8249-E7CDE48DA83F|
 | Configuration Manager 2409 | 3B7D84FA-ECCC-4EA0-B8AB-ABBDA1E88E0E |
 | Configuration Manager 2409 HFRU | 345A6BE1-3D07-43ED-B6E5-FAC0889DA04C |
-| Configuration Manager 2503 | 8576527E-DDE9-4146-8ED9-DB91091C38EF|
+| Configuration Manager 2503 | AA928926-5C76-4DE0-B51F-0FE4D365DFE2 |
 | Configuration Manager 2503 HFRU | 6B0783D9-B8A2-4848-82F6-8EFE956F4988|
 
 ### Identify the installation stage of the update

support/mem/intune/certificates/troubleshoot-scep-certificate-device-to-ndes.md

@@ -91,7 +91,7 @@ Key entries include the following sample text strings:
 
 ### Windows devices
 
-On a Windows device that is making a connection to NDES, you can view the devices Windows Event Viewer and look for indications of a successful connection. Connections are logged as an event ID **36** in the devices *DeviceManagement-Enterprise-Diagnostics-Provide* > **Admin** log.
+On a Windows device that is making a connection to NDES, you can view the devices Windows Event Viewer and look for indications of a successful connection. Connections are logged as an event ID **36** in the devices *DeviceManagement-Enterprise-Diagnostics-Provider* > **Admin** log.
 
 To open the log:
 
@@ -114,7 +114,7 @@ To open the log:
 
 ## Troubleshoot status code 500
 
-Connections that resemble the following example, with a status code of 500, indicate the *Impersonate a client after authentication* user right isn't assigned to the IIS_IUSRS group on the NDES server. The status value of **500** appears at the end:
+Connections that resemble the following example, and that have a status code of **500**, indicate the *Impersonate a client after authentication* user right isn't assigned to the IIS_IUSRS group on the NDES server. The status value of **500** appears at the end:
 
 ```output
 2017-08-08 20:22:16 IP_address GET /certsrv/mscep/mscep.dll operation=GetCACert&message=SCEP%20Authority 443 - 10.5.14.22 profiled/1.0+CFNetwork/811.5.4+Darwin/16.6.0 - 500 0 1346 31