various vs-azure-tools-xxx files

articles/vs-azure-tools-migrate-publish-web-app-to-cloud-service.md

@@ -12,7 +12,7 @@
    ms.topic="article"
    ms.tgt_pltfrm="na"
    ms.workload="multiple"
-   ms.date="05/08/2016"
+   ms.date="06/01/2016"
    ms.author="tarcher" />
 
 # How to: Migrate and Publish a Web Application to an Azure Cloud Service from Visual Studio

articles/vs-azure-tools-multiple-services-project-configurations.md

@@ -12,7 +12,7 @@
    ms.topic="article"
    ms.tgt_pltfrm="na"
    ms.workload="na"
-   ms.date="05/08/2016"
+   ms.date="06/01/2016"
    ms.author="tarcher" />
 
 # Configuring Your Azure Project Using Multiple Service Configurations
@@ -55,7 +55,7 @@ If you have already added an HTTPS endpoint, the HTTPS endpoint option is enable
 
 **Diagnostics**
 
-By default, diagnostics is enabled for the Web role. The Azure cloud service project and storage account are set to use the local storage emulator. When you are ready to deploy to Azure, you can click the builder button (**…**) to update the storage account to use Azure storage in the cloud. You can transfer the diagnostics data to the storage account on demand or at automatically scheduled intervals. For more information about Azure diagnostics, see [Enabling Diagnostics in Azure Cloud Services and Virtual Machines](./cloud-services/cloud-services-dotnet-diagnostics.md).
+By default, diagnostics is enabled for the Web role. The Azure cloud service project and storage account are set to use the local storage emulator. When you are ready to deploy to Azure, you can select the builder button (**…**) to update the storage account to use Azure storage in the cloud. You can transfer the diagnostics data to the storage account on demand or at automatically scheduled intervals. For more information about Azure diagnostics, see [Enabling Diagnostics in Azure Cloud Services and Virtual Machines](./cloud-services/cloud-services-dotnet-diagnostics.md).
 
 ## Settings page
 
@@ -67,7 +67,7 @@ A connection string is a configuration setting that provides connection and auth
 
 A connection string that points to an Azure storage account must use a defined format. For information about how to create connection strings, see [Configure Azure Storage Connection Strings](./storage/storage-configure-connection-string.md).
 
-When you are ready to test your service against the Azure storage services, or when you are ready to deploy your cloud service to Azure, you can change the value of any connection strings to point to your Azure storage account. Click (**…**), select **Enter storage account credentials**. Enter your account information that includes your account name and account key. In the **Storage Account Connection String** dialog box, you can also indicate whether you want to use the default HTTPS endpoints (the default option), the default HTTP endpoints, or custom endpoints. You might decide to use custom endpoints if you have registered a custom domain name for your service, as described in [Configure a custom domain name for blob data in an Azure storage account](./storage/storage-custom-domain-name.md).
+When you are ready to test your service against the Azure storage services, or when you are ready to deploy your cloud service to Azure, you can change the value of any connection strings to point to your Azure storage account. Select (**…**), select **Enter storage account credentials**. Enter your account information that includes your account name and account key. In the **Storage Account Connection String** dialog box, you can also indicate whether you want to use the default HTTPS endpoints (the default option), the default HTTP endpoints, or custom endpoints. You might decide to use custom endpoints if you have registered a custom domain name for your service, as described in [Configure a custom domain name for blob data in an Azure storage account](./storage/storage-custom-domain-name.md).
 
 >[AZURE.IMPORTANT] You must modify your connection strings to point to an Azure storage account before you deploy your service. Failing to do this may cause your role not to start, or to cycle through the initializing, busy, and stopping states.
 

articles/vs-azure-tools-publishing-a-cloud-service.md

@@ -12,7 +12,7 @@
    ms.topic="article"
    ms.tgt_pltfrm="na"
    ms.workload="multiple"
-   ms.date="05/08/2016"
+   ms.date="06/01/2016"
    ms.author="tarcher" />
 
 # Publishing a Cloud Service using the Azure Tools
@@ -49,7 +49,7 @@ When you publish your Azure application, you can do one of the following tasks:
 
   1. In the **Package Azure Application** dialog box, choose the service configuration for which you want to create a package, and then choose the build configuration.
 
-  1. (optional) To turn on Remote Desktop for the cloud service after you publish it, select the **Enable Remote Desktop for all Roles** check box, and then click **Settings** to configure Remote Desktop. If you want to debug your cloud service after you publish it, turn on remote debugging by selecting **Enable Remote Debugger for all Roles**.
+  1. (optional) To turn on Remote Desktop for the cloud service after you publish it, select the **Enable Remote Desktop for all Roles** check box, and then select **Settings** to configure Remote Desktop. If you want to debug your cloud service after you publish it, turn on remote debugging by selecting **Enable Remote Debugger for all Roles**.
 
       For more information, see [Using Remote Desktop with Azure Roles](vs-azure-tools-using-remote-desktop-with-azure-roles.md).
 
@@ -97,7 +97,7 @@ The following procedure assumes that you are using the **Publish Azure Applicati
 
     The cloud service is published. The virtual machine that is created has remote connections enabled for IIS so that Web Deploy can be used to update your web roles without republishing them.
 
-    >[AZURE.NOTE] If you have more than one instance configured for a web role, a warning message appears, stating that each web role will be limited to one instance only in the package that’s created to publish your application. Click OK to continue. As stated in the Requirements section, you can have more than one web role but only one instance of each role.
+    >[AZURE.NOTE] If you have more than one instance configured for a web role, a warning message appears, stating that each web role will be limited to one instance only in the package that’s created to publish your application. Select **OK** to continue. As stated in the Requirements section, you can have more than one web role but only one instance of each role.
 
 ### To Update Your Web Role by Using Web Deploy
 
@@ -125,7 +125,7 @@ The following procedure assumes that you are using the **Publish Azure Applicati
 
 1. To add a trusted SSL certificate to IIS to use for remote connections, follow these steps:
 
-  1. To connect to the virtual machine that is running the web role, click the instance of the web role in **Cloud Explorer** or **Server Explorer**, and then choose the **Connect using Remote Desktop** command. For detailed steps about how to connect to the virtual machine, see [Using Remote Desktop with Azure Roles](vs-azure-tools-remote-desktop-roles.md).
+  1. To connect to the virtual machine that is running the web role, select the instance of the web role in **Cloud Explorer** or **Server Explorer**, and then choose the **Connect using Remote Desktop** command. For detailed steps about how to connect to the virtual machine, see [Using Remote Desktop with Azure Roles](vs-azure-tools-remote-desktop-roles.md).
 
       Your browser will prompt you to download an .RDP file.
 

articles/vs-azure-tools-service-configurations-and-profiles-how-to-manage.md

@@ -12,7 +12,7 @@
    ms.topic="article"
    ms.tgt_pltfrm="na"
    ms.workload="multiple"
-   ms.date="04/18/2016"
+   ms.date="06/01/2016"
    ms.author="tarcher" />
 
 # How to manage service configurations and profiles
@@ -29,47 +29,47 @@ You can add, delete, rename, and modify these service configurations based on yo
 
 ![Manage Service Configurations](./media/vs-azure-tools-service-configurations-and-profiles-how-to-manage/manage-service-config.png)
 
-You can also open the **Manage Configurations** dialog box from the role’s property pages. To open the properties for a role in your Azure project, open the shortcut menu for that role, and then choose **Properties**. On the **Settings** tab, expand the **Service Configuration** list, and then click **Manage** to open the **Manage Configurations** dialog box.
+You can also open the **Manage Configurations** dialog box from the role’s property pages. To open the properties for a role in your Azure project, open the shortcut menu for that role, and then choose **Properties**. On the **Settings** tab, expand the **Service Configuration** list, and then select **Manage** to open the **Manage Configurations** dialog box.
 
 ### To add a service configuration
 
-1. In Solution Explorer open the shortcut menu for the Azure project and then click **Manage Configurations**.
+1. In Solution Explorer open the shortcut menu for the Azure project and then select **Manage Configurations**.
 
     The **Manage Service Configurations** dialog box appears.
 
-1. To add a service configuration, you must create a copy of an existing configuration. To do this, choose the configuration that you want to copy from the Name list and then click **Create copy**.
+1. To add a service configuration, you must create a copy of an existing configuration. To do this, choose the configuration that you want to copy from the Name list and then select **Create copy**.
 
-1. (Optional) To give the service configuration a different name, choose the new service configuration from the Name list and then click **Rename**. In the **Name** text box, type the name that you want to use for this service configuration and then click **OK**.
+1. (Optional) To give the service configuration a different name, choose the new service configuration from the Name list and then select **Rename**. In the **Name** text box, type the name that you want to use for this service configuration and then select **OK**.
 
     A new service configuration file that is named ServiceConfiguration.[New Name].cscfg is added to the Azure project in Solution Explorer.
 
 
 ### To delete a service configuration
 
-1. In Solution Explorer, open the shortcut menu for the Azure project and then click **Manage Configurations**.
+1. In Solution Explorer, open the shortcut menu for the Azure project and then select **Manage Configurations**.
 
     The **Manage Service Configurations** dialog box appears.
 
-1. To delete a service configuration, choose the configuration that you want to delete from the **Name** list and then click **Remove**. A dialog box appears to verify that you want to delete this configuration.
+1. To delete a service configuration, choose the configuration that you want to delete from the **Name** list and then select **Remove**. A dialog box appears to verify that you want to delete this configuration.
 
-1. Click **Delete**.
+1. Select **Delete**.
 
      The service configuration file is removed from the Azure project in Solution Explorer.
 
 
 ### To rename a service configuration
 
-1. In Solution Explorer, open the shortcut menu for the Azure project and then click **Manage Configurations**.
+1. In Solution Explorer, open the shortcut menu for the Azure project, and then select **Manage Configurations**.
 
     The **Manage Service Configurations** dialog box appears.
 
-1. To rename a service configuration, choose the new service configuration from the **Name** list and then click **Rename**. In the **Name** text box, type the name that you want to use for this service configuration and then click **OK**.
+1. To rename a service configuration, choose the new service configuration from the **Name** list, and then select **Rename**. In the **Name** text box, type the name that you want to use for this service configuration, and then select **OK**.
 
     The name of the service configuration file is changed in the Azure project in Solution Explorer.
 
 ### To change a service configuration
 
-- If you want to change a service configuration, open the shortcut menu for the specific role you want to change in the Azure project and then click Properties. See [How to: Configure the Roles for an Azure Cloud Service with Visual Studio](https://msdn.microsoft.com/library/azure/hh369931.aspx) for more information.
+- If you want to change a service configuration, open the shortcut menu for the specific role you want to change in the Azure project, and then select **Properties**. See [How to: Configure the Roles for an Azure Cloud Service with Visual Studio](https://msdn.microsoft.com/library/azure/hh369931.aspx) for more information.
 
 ## Make different setting combinations by using profiles
 
@@ -79,53 +79,53 @@ When you run the wizard for the first time, a default profile is created. Visual
 
 ### To add a profile
 
-1. Open the shortcut menu for your Azure project, and then click **Publish**.
+1. Open the shortcut menu for your Azure project, and then select **Publish**.
 
-1. Next to the **Target profile** list, click the **Save Profile** button, as the following illustration shows. This creates a profile for you.
+1. Next to the **Target profile** list, select the **Save Profile** button, as the following illustration shows. This creates a profile for you.
 
     ![Create an new profile](./media/vs-azure-tools-service-configurations-and-profiles-how-to-manage/create-new-profile.png)
 
-1. After the profile is created, click **<Manage…>** in the **Target profile** list.
+1. After the profile is created, select **<Manage…>** in the **Target profile** list.
 
     The **Manage Profiles** dialog box appears, as the following illustration shows.
 
     ![Manage Profiles Dialog](./media/vs-azure-tools-service-configurations-and-profiles-how-to-manage/manage-profiles.png)
 
-1. In the **Name** list, choose a profile, and then click **Create Copy**.
+1. In the **Name** list, choose a profile, and then select **Create Copy**.
 
 1. Choose the **Close** button.
 
     The new profile appears in the Target profile list.
 
-1. In the **Target profile** list, click the profile that you just created. The Publish Wizard settings are filled in with the choices from the profile you selected.
+1. In the **Target profile** list, select the profile that you just created. The Publish Wizard settings are filled in with the choices from the profile you selected.
 
-1. Click the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then customize the settings for this profile. See [Publish Azure Application Wizard](http://go.microsoft.com/fwlink/p/?LinkID=623085) for information.
+1. Select the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then customize the settings for this profile. See [Publish Azure Application Wizard](http://go.microsoft.com/fwlink/p/?LinkID=623085) for information.
 
-1. After you finish customizing the settings, click **Next** to go back to the Settings page. The profile is saved when you publish the service by using these settings or if you click **Save** next to the list of profiles.
+1. After you finish customizing the settings, select **Next** to go back to the Settings page. The profile is saved when you publish the service by using these settings or if you select **Save** next to the list of profiles.
 
 ### To rename or delete a profile
 
-1. Open the shortcut menu for your Azure project, and then click **Publish**.
+1. Open the shortcut menu for your Azure project, and then select **Publish**.
 
-1. In the **Target profile** list, click **Manage**.
+1. In the **Target profile** list, select **Manage**.
 
-1. In the **Manage Profiles** dialog box, click the profile that you want to delete, and then click **Remove**.
+1. In the **Manage Profiles** dialog box, select the profile that you want to delete, and then select **Remove**.
 
-1. In the confirmation dialog box that appears, click **OK**.
+1. In the confirmation dialog box that appears, select **OK**.
 
-1. Click **Close**.
+1. Select **Close**.
 
 ### To change a profile
 
-1. Open the shortcut menu for your Azure project, and then click **Publish**.
+1. Open the shortcut menu for your Azure project, and then select **Publish**.
 
-1. In the **Target profile** list, click the profile that you want to change.
+1. In the **Target profile** list, select the profile that you want to change.
 
-1. Click the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then change the settings you want. See [Publish Azure Application Wizard](http://go.microsoft.com/fwlink/p/?LinkID=623085) for information.
+1. Select the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then change the settings you want. See [Publish Azure Application Wizard](http://go.microsoft.com/fwlink/p/?LinkID=623085) for information.
 
-1. After you finish changing the settings, click **Next** to go back to the **Settings** page.
+1. After you finish changing the settings, select **Next** to go back to the **Settings** page.
 
-1. (Optional) Click **Publish** to publish the cloud service using the new settings. If you don’t want to publish your cloud service at this time, and you close the Publish Wizard, Visual Studio asks you if you want to save the changes to the profile.
+1. (Optional) select **Publish** to publish the cloud service using the new settings. If you don’t want to publish your cloud service at this time, and you close the Publish Wizard, Visual Studio asks you if you want to save the changes to the profile.
 
 ## Next steps
 

articles/vs-azure-tools-storage-emulator-using.md

@@ -12,7 +12,7 @@
    ms.topic="article"
    ms.tgt_pltfrm="na"
    ms.workload="na"
-   ms.date="05/08/2016"
+   ms.date="06/01/2016"
    ms.author="tarcher" />
 
 # Configuring and Using the Storage Emulator with Visual Studio