more

Author: meganbradley

articles/site-recovery/physical-manage-configuration-server.md

@@ -34,7 +34,7 @@ The table summarizes the prerequisites for deploying the on-premises configurati
 | IIS | - No pre-existing default website <br> - Enable  [Anonymous Authentication](https://technet.microsoft.com/library/cc731244(v=ws.10).aspx) <br> - Enable [FastCGI](https://technet.microsoft.com/library/cc753077(v=ws.10).aspx) setting  <br> - No pre-existing website/application listening on port 443<br>|
 | NIC type | VMXNET3 (when deployed as a VMware VM) |
 | IP address type | Static |
-| Internet access | The server needs access to these URLs: <br> - \*.accesscontrol.windows.net<br> - \*.backup.windowsazure.com <br>- \*.store.core.windows.net<br> - \*.blob.core.windows.net<br> - \*.hypervrecoverymanager.windowsazure.com <br> - https://management.azure.com <br> - *.services.visualstudio.com <br> - https://dev.mysql.com/get/Downloads/MySQLInstaller/mysql-installer-community-5.7.20.0.msi (not required for Scale-out Process Servers) <br> - time.nist.gov <br> - time.windows.com |
+| Internet access | The server needs access to these URLs: <br> - \*.accesscontrol.windows.net<br> - \*.backup.windowsazure.com <br>- \*.store.core.windows.net<br> - \*.blob.core.windows.net<br> - \*.hypervrecoverymanager.windowsazure.com <br> - `https://management.azure.com` <br> - *.services.visualstudio.com <br> - https://dev.mysql.com/get/Downloads/MySQLInstaller/mysql-installer-community-5.7.20.0.msi (not required for Scale-out Process Servers) <br> - time.nist.gov <br> - time.windows.com |
 | Ports | 443 (Control channel orchestration)<br>9443 (Data transport)|
 
 ## Download the latest installation file
@@ -55,7 +55,7 @@ The latest version of the configuration server installation file is available in
 1. Run the Unified Setup installation file.
 2. In **Before You Begin**, select **Install the configuration server and process server**.
 
-	![Before you start](./media/physical-manage-configuration-server/combined-wiz1.png)
+    ![Before you start](./media/physical-manage-configuration-server/combined-wiz1.png)
 
 3. In **Third Party Software License**, click **I Accept** to download and install MySQL.
 4. In **Internet Settings**, specify how the Provider running on the configuration server connects to Azure Site Recovery over the Internet. Make sure you've allowed the required URLs.

articles/storage/common/storage-ref-azcopy-login.md

@@ -96,7 +96,7 @@ Make sure to treat /path/to/my/cert as a path to a PEM or PKCS12 file. AzCopy do
 
 |Option|Description|
 |--|--|
-|--aad-endpoint|The Azure Active Directory endpoint to use. The default (https://login.microsoftonline.com) is correct for the public Azure cloud. Set this parameter when authenticating in a national cloud. See [Azure AD authentication endpoints](https://docs.microsoft.com/azure/active-directory/develop/authentication-national-cloud#azure-ad-authentication-endpoints).
+|--aad-endpoint|The Azure Active Directory endpoint to use. The default (`https://login.microsoftonline.com`) is correct for the public Azure cloud. Set this parameter when authenticating in a national cloud. See [Azure AD authentication endpoints](https://docs.microsoft.com/azure/active-directory/develop/authentication-national-cloud#azure-ad-authentication-endpoints).
 This flag is not needed for Managed Service Identity.|
 |--application-id string|Application ID of user-assigned identity. Required for service principal auth.|
 |--certificate-path string|Path to certificate for SPN authentication. Required for certificate-based service principal auth.|

articles/storage/files/storage-sync-files-firewall-and-proxy.md

@@ -86,8 +86,8 @@ The following table describes the required domains for communication:
 
 | Service | Public cloud endpoint | Azure Government endpoint | Usage |
 |---------|----------------|---------------|------------------------------|
-| **Azure Resource Manager** | https://management.azure.com | https://management.usgovcloudapi.net | Any user call (like PowerShell) goes to/through this URL, including the initial server registration call. |
-| **Azure Active Directory** | https://login.windows.net<br>https://login.microsoftonline.com | https://login.microsoftonline.us | Azure Resource Manager calls must be made by an authenticated user. To succeed, this URL is used for user authentication. |
+| **Azure Resource Manager** | `https://management.azure.com` | https://management.usgovcloudapi.net | Any user call (like PowerShell) goes to/through this URL, including the initial server registration call. |
+| **Azure Active Directory** | https://login.windows.net<br>`https://login.microsoftonline.com` | https://login.microsoftonline.us | Azure Resource Manager calls must be made by an authenticated user. To succeed, this URL is used for user authentication. |
 | **Azure Active Directory** | https://graph.microsoft.com/ | https://graph.microsoft.com/ | As part of deploying Azure File Sync, a service principal in the subscription's Azure Active Directory will be created. This URL is used for that. This principal is used for delegating a minimal set of rights to the Azure File Sync service. The user performing the initial setup of Azure File Sync must be an authenticated user with subscription owner privileges. |
 | **Azure Storage** | &ast;.core.windows.net | &ast;.core.usgovcloudapi.net | When the server downloads a file, then the server performs that data movement more efficiently when talking directly to the Azure file share in the Storage Account. The server has a SAS key that only allows for targeted file share access. |
 | **Azure File Sync** | &ast;.one.microsoft.com<br>&ast;.afs.azure.net | &ast;.afs.azure.us | After initial server registration, the server receives a regional URL for the Azure File Sync service instance in that region. The server can use the URL to communicate directly and efficiently with the instance handling its sync. |

articles/stream-analytics/stream-analytics-cicd-api.md

@@ -52,7 +52,7 @@ To create Stream Analytics job, call the PUT method using the Stream Analytics A
 
 |Method|Request URL|
 |------|-----------|
-|PUT|https://management.azure.com/subscriptions/{**subscription-id**}/resourcegroups/{**resource-group-name**}/providers/Microsoft.StreamAnalytics/streamingjobs/{**job-name**}?api-version=2017-04-01-preview|
+|PUT|`https://management.azure.com/subscriptions/{\**subscription-id**}/resourcegroups/{**resource-group-name**}/providers/Microsoft.StreamAnalytics/streamingjobs/{**job-name**}?api-version=2017-04-01-preview`|
  
 Example of command using **curl**:
 
@@ -139,7 +139,7 @@ To publish a Stream Analytics job on IoT Edge, call the POST method using the Ed
 
 |Method|Request URL|
 |------|-----------|
-|POST|https://management.azure.com/subscriptions/{**subscriptionid**}/resourceGroups/{**resourcegroupname**}/providers/Microsoft.StreamAnalytics/streamingjobs/{**jobname**}/publishedgepackage?api-version=2017-04-01-preview|
+|POST|`https://management.azure.com/subscriptions/{\**subscriptionid**}/resourceGroups/{**resourcegroupname**}/providers/Microsoft.StreamAnalytics/streamingjobs/{**jobname**}/publishedgepackage?api-version=2017-04-01-preview`|
 
 This asynchronous operation returns a status of 202 until the job has been successfully published. The location response header contains the URI used to get the status of the process. While the process is running, a call to the URI in the location header returns a status of 202. When the process finishes, the URI in the location header returns a status of 200. 
 

articles/traffic-manager/traffic-manager-how-it-works.md

@@ -29,7 +29,7 @@ When a client attempts to connect to a service, it must first resolve the DNS na
 
 ## Traffic Manager example
 
-Contoso Corp have developed a new partner portal. The URL for this portal is https://partners.contoso.com/login.aspx. The application is hosted in three regions of Azure. To improve availability and maximize global performance, they use Traffic Manager to distribute client traffic to the closest available endpoint.
+Contoso Corp have developed a new partner portal. The URL for this portal is `https://partners.contoso.com/login.aspx`. The application is hosted in three regions of Azure. To improve availability and maximize global performance, they use Traffic Manager to distribute client traffic to the closest available endpoint.
 
 To achieve this configuration, they complete the following steps:
 
@@ -44,7 +44,7 @@ To achieve this configuration, they complete the following steps:
 
 ### How clients connect using Traffic Manager
 
-Continuing from the previous example, when a client requests the page https://partners.contoso.com/login.aspx, the client performs the following steps to resolve the DNS name and establish a connection:
+Continuing from the previous example, when a client requests the page `https://partners.contoso.com/login.aspx`, the client performs the following steps to resolve the DNS name and establish a connection:
 
 ![Connection establishment using Traffic Manager][2]
 

articles/traffic-manager/traffic-manager-point-internet-domain.md

@@ -18,7 +18,7 @@ When you create a Traffic Manager profile, Azure automatically assigns a DNS nam
 
 For example, to point name `www.contoso.com` to the Traffic Manager DNS name `contoso.trafficmanager.net`, you create the following DNS resource record:
 
-    www.contoso.com IN CNAME contoso.trafficmanager.net
+    `www.contoso.com IN CNAME contoso.trafficmanager.net`
 
 All traffic requests to *www\.contoso.com* get directed to *contoso.trafficmanager.net*.
 

articles/virtual-desktop/create-host-pools-arm-template.md

@@ -38,7 +38,7 @@ If you're deploying in a Cloud Solution Provider subscription, follow these step
 
 1. Scroll down and right-click **Deploy to Azure**, then select **Copy Link Location**.
 2. Open a text editor like Notepad and paste the link there.
-3. Right after "https://portal.azure.com/" and before the hashtag (#) enter an at sign (@) followed by the tenant domain name. Here's an example of the format you should use: https://portal.azure.com/@Contoso.onmicrosoft.com#create/.
+3. Right after "https://portal.azure.com/" and before the hashtag (#) enter an at sign (@) followed by the tenant domain name. Here's an example of the format you should use: `https://portal.azure.com/@Contoso.onmicrosoft.com#create/`.
 4. Sign in to the Azure portal as a user with Admin/Contributor permissions to the Cloud Solution Provider subscription.
 5. Paste the link you copied to the text editor into the address bar.
 

articles/virtual-machines/linux/cloudfoundry-deploy-your-first-app.md

@@ -22,7 +22,7 @@ There are several options for creating a Cloud Foundry environment on Azure:
 - [Deploy the open-source Cloud Foundry packages directly][oss-cf-bosh] by setting up a [BOSH](https://bosh.io) director, a VM that coordinates the deployment of the Cloud Foundry environment.
 
 > [!IMPORTANT] 
-> If you are deploying PCF from the Azure Marketplace, make a note of the SYSTEMDOMAINURL and the admin credentials required to access the Pivotal Apps Manager, both of which are described in the marketplace deployment guide. They are needed to complete this tutorial. For marketplace deployments, the SYSTEMDOMAINURL is in the form https://system.*ip-address*.cf.pcfazure.com.
+> If you are deploying PCF from the Azure Marketplace, make a note of the SYSTEMDOMAINURL and the admin credentials required to access the Pivotal Apps Manager, both of which are described in the marketplace deployment guide. They are needed to complete this tutorial. For marketplace deployments, the SYSTEMDOMAINURL is in the form `https://system.*ip-address*.cf.pcfazure.com`.
 
 ## Connect to the Cloud Controller
 

articles/virtual-machines/linux/openshift-container-platform-3x-post-deployment.md

@@ -36,9 +36,9 @@ To use Azure Active Directory for authentication, first you need to create an Az
 These steps use the Azure CLI to create the app registration, and the GUI (portal) to set the permissions. To create the app registration, you need the following five pieces of information:
 
 - Display name: App registration name (for example, OCPAzureAD)
-- Home page: OpenShift console URL (for example, https://masterdns343khhde.westus.cloudapp.azure.com/console)
-- Identifier URI: OpenShift console URL (for example, https://masterdns343khhde.westus.cloudapp.azure.com/console)
-- Reply URL: Master public URL and the app registration name (for example, https://masterdns343khhde.westus.cloudapp.azure.com/oauth2callback/OCPAzureAD)
+- Home page: OpenShift console URL (for example, `https://masterdns343khhde.westus.cloudapp.azure.com/console`)
+- Identifier URI: OpenShift console URL (for example, `https://masterdns343khhde.westus.cloudapp.azure.com/console`)
+- Reply URL: Master public URL and the app registration name (for example, `https://masterdns343khhde.westus.cloudapp.azure.com/oauth2callback/OCPAzureAD`)
 - Password: Secure password (use a strong password)
 
 The following example creates an app registration by using the preceding information:

articles/virtual-machines/linux/quick-create-portal.md

@@ -85,7 +85,7 @@ Create an SSH connection with the VM.
     ssh [email protected]
     ```
 
-3. Using the same bash shell you used to create your SSH key pair (you can reopen the Cloud Shell by selecting `>_` again or going to https://shell.azure.com/bash), paste the SSH connection command into the shell to create an SSH session.
+3. Using the same bash shell you used to create your SSH key pair (you can reopen the Cloud Shell by selecting `>_` again or going to `https://shell.azure.com/bash`), paste the SSH connection command into the shell to create an SSH session.
 
 ## Install web server