Merge pull request #245451 from halkazwini/bastion-troubleshoot

Bastion troubleshoot update

Author: prmerger-automator[bot]

articles/bastion/troubleshoot.md

@@ -15,9 +15,9 @@ This article shows you how to troubleshoot Azure Bastion.
 
 ## <a name="nsg"></a>Unable to create an NSG on AzureBastionSubnet
 
-**Q:** When I try to create an NSG on the Azure Bastion subnet, I get the following error: *'Network security group \<NSG name\> does not have necessary rules for Azure Bastion Subnet AzureBastionSubnet"*.
+**Q:** When I try to create an NSG on the Azure Bastion subnet, I get the following error: *'Network security group \<NSG name\> doesn't have necessary rules for Azure Bastion Subnet AzureBastionSubnet"*.
 
-**A:** If you create and apply an NSG to *AzureBastionSubnet*, make sure you have added the required rules to the NSG. For a list of required rules, see [Working with NSG access and Azure Bastion](./bastion-nsg.md). If you do not add these rules, the NSG creation/update will fail.
+**A:** If you create and apply an NSG to *AzureBastionSubnet*, make sure you have added the required rules to the NSG. For a list of required rules, see [Working with NSG access and Azure Bastion](./bastion-nsg.md). If you don't add these rules, the NSG creation/update will fail.
 
 An example of the NSG rules is available for reference in the [quickstart template](https://azure.microsoft.com/resources/templates/azure-bastion-nsg/).
 For more information, see [NSG guidance for Azure Bastion](bastion-nsg.md).
@@ -26,7 +26,7 @@ For more information, see [NSG guidance for Azure Bastion](bastion-nsg.md).
 
 **Q:** When I try to browse my SSH key file, I get the following error: *'SSH Private key must start with -----BEGIN RSA/DSA/OPENSSH PRIVATE KEY----- and ends with -----END RSA/DSA/OPENSSH PRIVATE KEY-----'*.
 
-**A:** Azure Bastion supports RSA, DSA, and OPENSSH private keys, at this point in time. Make sure that you browse a key file that is RSA, DSA, or OPENSSH private key for SSH, with public key provisioned on the target VM. 
+**A:** Azure Bastion currently supports RSA, DSA, and OPENSSH private keys. Make sure that you browse a key file that is RSA, DSA, or OPENSSH private key for SSH, with public key provisioned on the target VM. 
 
 As an example, you can use the following command to create a new RSA SSH key:
 
@@ -60,28 +60,28 @@ The key's randomart image is:
 
 ## <a name="domain"></a>Unable to sign in to my Windows domain-joined virtual machine
 
-**Q:** I am unable to connect to my Windows virtual machine that is domain-joined.
+**Q:** I'm unable to connect to my Windows virtual machine that is domain-joined.
 
-**A:** Azure Bastion supports domain-joined VM sign-in for username-password based domain sign-in only. When specifying the domain credentials in  the Azure portal, use the UPN (username@domain) format instead of *domain\username* format to sign in. This is supported for domain-joined or hybrid-joined (both domain-joined as well as Azure AD-joined) virtual machines. It is not supported for Azure AD-joined-only virtual machines.
+**A:** Azure Bastion supports domain-joined VM sign-in for username-password based domain sign-in only. When specifying the domain credentials in  the Azure portal, use the UPN (username@domain) format instead of *domain\username* format to sign in. This is supported for domain-joined or hybrid-joined (both domain-joined and Azure AD-joined) virtual machines. It isn't supported for Azure AD-joined-only virtual machines.
 
 ## <a name="connectivity"></a> Unable to connect to virtual machine
 
-**Q:** I am unable to connect to my virtual machine (and I'm not experiencing the problems above).
+**Q:** I'm unable to connect to my virtual machine (and I'm not experiencing the problems above).
 
-**A:** You can troubleshoot your connectivity issues by navigating to the **Connection Troubleshoot** tab (in the **Monitoring** section) of your Azure Bastion resource in the Azure portal. Network Watcher Connection Troubleshoot provides the capability to check a direct TCP connection from a virtual machine (VM) to a VM, fully qualified domain name (FQDN), URI, or IPv4 address. To start, choose a source to start the connection from, and the destination you wish to connect to and select "Check". [Learn more](../network-watcher/network-watcher-connectivity-overview.md).
+**A:** You can troubleshoot your connectivity issues by navigating to the **Connection Troubleshoot** tab (in the **Monitoring** section) of your Azure Bastion resource in the Azure portal. Network Watcher Connection Troubleshoot provides the capability to check a direct TCP connection from a virtual machine (VM) to a VM, fully qualified domain name (FQDN), URI, or IPv4 address. To start, choose a source to start the connection from, and the destination you wish to connect to and select "Check". For more information, see [Connection Troubleshoot](../network-watcher/network-watcher-connectivity-overview.md).
 
 
 ## <a name="filetransfer"></a>File transfer issues
 
 **Q:** Is file transfer supported with Azure Bastion?
 
-**A:** File transfer is not supported at this time. We are working on adding support.
+**A:** File transfer isn't supported at this time. We're working on adding support.
 
 ## <a name="blackscreen"></a>Black screen in the Azure portal
 
-**Q:** When I try to connect using Azure Bastion, I can't connect to the target VM and I get a black screen in the Azure portal.
+**Q:** When I try to connect using Azure Bastion, I can't connect to the target VM, and I get a black screen in the Azure portal.
 
-**A:** This happens when there is either a network connectivity issue between your web browser and Azure Bastion (your client Internet firewall may be blocking WebSockets traffic or similar), or between the Azure Bastion and your target VM. Most cases include an NSG applied either to AzureBastionSubnet, or on your target VM subnet that is blocking the RDP/SSH traffic in your virtual network. Allow WebSockets traffic on your client internet firewall, and check the NSGs on your target VM subnet.
+**A:** This happens when there's either a network connectivity issue between your web browser and Azure Bastion (your client Internet firewall may be blocking WebSockets traffic or similar), or between the Azure Bastion and your target VM. Most cases include an NSG applied either to AzureBastionSubnet, or on your target VM subnet that is blocking the RDP/SSH traffic in your virtual network. Allow WebSockets traffic on your client internet firewall, and check the NSGs on your target VM subnet. See [Unable to connect to virtual machine](#connectivity) to learn how to use **Connection Troubleshoot** to troubleshoot your connectivity issues.
 
 ## Next steps