diff --git a/windows-365/enterprise/partner-integration-scenarios.md b/windows-365/enterprise/partner-integration-scenarios.md
index 3a8078845c9..04c8f71bcb3 100644
--- a/windows-365/enterprise/partner-integration-scenarios.md
+++ b/windows-365/enterprise/partner-integration-scenarios.md
@@ -52,7 +52,7 @@ While scenarios not listed here might still work in customers’ production envi
 1. A user authenticates using Microsoft Entra ID, on-premises Active Directory, or a third party identity provider.
 2. Windows 365 establishes a connection to the partner cloud gateway using partner protocols.
 3. A Cloud PC is assigned to the user and is accessible from the web/workspace portals.
-4. Windows 365 establishes a connection to the Cloud PC using partner protocols.
+4. Windows 365 establishes a connection to the Cloud PC using partner protocols. 
 
 <!-- ########################## -->
 ## Next steps
diff --git a/windows-365/enterprise/provisioning-errors.md b/windows-365/enterprise/provisioning-errors.md
index 954ece6646d..cdd3421b403 100644
--- a/windows-365/enterprise/provisioning-errors.md
+++ b/windows-365/enterprise/provisioning-errors.md
@@ -184,6 +184,10 @@ If you are seeing this error, some factors to consider are:
 - If the device is Intune-enrolled, you can apply Intune policy to disable the ports.
 - The user can also disable the ports manually by adding a local firewall rule onto their device. For a list of high risk ports that are recommended for blocking, please see [Security admin rules in Azure Virtual Network Manager](/azure/virtual-network-manager/concept-security-admins#protect-high-risk-ports).
 
+## Other provisioning failures
+
+If you encounter other provisioning errors not covered above, make sure all the required endpoints are allowed on the VNet used for your ANC and any gateway device.
+
 <!-- ########################## -->
 ## Next steps
 [Troubleshooting](troubleshooting.md).