edits, bookmark updates in 2 other files

Author: ktoliver

articles/cloud-services-extended-support/deploy-portal.md

@@ -1,15 +1,15 @@
 ---
 title: Deploy Azure Cloud Services (extended support) - Azure portal
-description: Deploy an Azure Cloud Service (extended support) using the Azure portal.
+description: Deploy Azure Cloud Services (extended support) by using the Azure portal.
 ms.topic: quickstart
 ms.service: cloud-services-extended-support
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 10/13/2020
+ms.date: 06/18/2024
 ---
 
-# Deploy Azure Cloud Services (extended support) by using the Azure portal
+# Deploy Cloud Services (extended support) by using the Azure portal
 
 This article shows you how to use the Azure portal to create an Azure Cloud Services (extended support) deployment.
 
@@ -41,7 +41,7 @@ Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services
 
     :::image type="content" source="media/deploy-portal-3.png" alt-text="Image shows the Cloud Services (extended support) Basics tab.":::
 
-1. On the **Basics** tab under **Cloud service configuration, package, and service definition**, add your package (.cspkg, .zip) file, configuration (.cscfg) file, and definition (.csdef) file for the deployment. You can add existing files from blob storage or upload the files from your local machine. If you upload the files from your local machine, the files are stored in a storage account in Azure.
+1. On the **Basics** tab under **Cloud service configuration, package, and service definition**, add your package (.cspkg or .zip) file, configuration (.cscfg) file, and definition (.csdef) file for the deployment. You can add existing files from blob storage or upload the files from your local machine. If you upload the files from your local machine, the files are stored in a storage account in Azure.
 
     :::image type="content" source="media/deploy-portal-4.png" alt-text="Screenshot that shows the section of the Basics tab where you upload files and select storage.":::
 

articles/cloud-services-extended-support/deploy-powershell.md

@@ -1,18 +1,18 @@
 ---
 title: Deploy Azure Cloud Services (extended support) - Azure PowerShell
-description: Deploy an Azure Cloud Service (extended support) using Azure PowerShell
+description: Deploy Azure Cloud Services (extended support) by using Azure PowerShell.
 ms.topic: quickstart
 ms.service: cloud-services-extended-support
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 10/13/2020
+ms.date: 06/18/2024
 ms.custom: devx-track-azurepowershell
 ---
 
-# Deploy a Cloud Service (extended support) by using Azure PowerShell
+# Deploy Cloud Services (extended support) by using Azure PowerShell
 
-This article shows how to use the Az.CloudService Azure PowerShell module to create an Azure Cloud Services (extended support) deployment that has multiple roles (WebRole and WorkerRole).
+This article shows you how to use the Az.CloudService Azure PowerShell module to create an Azure Cloud Services (extended support) deployment that has multiple roles (WebRole and WorkerRole).
 
 ## Prerequisites
 
@@ -32,7 +32,7 @@ Complete the following steps as prerequisites to creating your deployment by usi
     New-AzResourceGroup -ResourceGroupName “ContosOrg” -Location “East US” 
     ```
 
-1. Create a storage account and container in Azure to store the package (.cspkg) file and configuration (.cscfg) file for the Cloud Services (extended support) deployment. You must use a unique name for the storage account name. This step is optional if you use an existing storage account.
+1. Create a storage account and container in Azure to store the package (.cspkg or .zip) file and configuration (.cscfg) file for the Cloud Services (extended support) deployment. You must use a unique name for the storage account name. This step is optional if you use an existing storage account.
 
     ```azurepowershell-interactive
     $storageAccount = New-AzStorageAccount -ResourceGroupName “ContosOrg” -Name “contosostorageaccount” -Location “East US” -SkuName “Standard_RAGRS” -Kind “StorageV2” 
@@ -45,7 +45,7 @@ Use any of the following Azure PowerShell cmdlets to deploy Cloud Services (exte
 
 - Quick-create a deployment by using a [storage account](#quick-create-a-deployment-by-using-a-storage-account)
 
-  - This parameter set inputs the package (.cspkg) file, configuration (.cscfg) file, and definition (.csdef) file for the deployment as inputs with the storage account.
+  - This parameter set inputs the package (.cspkg or .zip) file, the configuration (.cscfg) file, and the definition (.csdef) file for the deployment as inputs with the storage account.
   - The Cloud Services (extended support) role profile, network profile, and OS profile are created by the cmdlet with minimal input.
   - To input a certificate, you must specify a key vault name. The certificate thumbprints in the key vault are validated against the certificates that you specify in the configuration (.cscfg) file for the deployment.
 
@@ -152,7 +152,7 @@ New-AzCloudService
     $networkProfile = @{loadBalancerConfiguration = $loadBalancerConfig} 
     ```
 
-1. Create a key vault. The key vault stores certificates that are associated with Cloud Service (extended support) roles. The key vault must be in the same region and subscription as the Cloud Service (extended support) deployment and have a unique name. For more information, see [Use certificates with Azure Cloud Services (extended support)](certificates-and-key-vault.md).
+1. Create a key vault. The key vault stores certificates that are associated with Cloud Services (extended support) roles. The key vault must be in the same region and subscription as the Cloud Services (extended support) deployment and have a unique name. For more information, see [Use certificates with Cloud Services (extended support)](certificates-and-key-vault.md).
 
     ```azurepowershell-interactive
     New-AzKeyVault -Name "ContosKeyVault” -ResourceGroupName “ContosOrg” -Location “East US” 
@@ -171,7 +171,7 @@ New-AzCloudService
     Set-AzKeyVaultAccessPolicy -VaultName 'ContosKeyVault' -ResourceGroupName 'ContosOrg' -ObjectId 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' -PermissionsToCertificates create,get,list,delete 
     ```
 
-1. In this example, you add a self-signed certificate to a key vault. You must add the certificate thumbprint via the deployment configuration (.cscfg) file for Cloud Services (extended support) roles.
+1. Th following example adds a self-signed certificate to a key vault. You must add the certificate thumbprint via the configuration (.cscfg) file for Cloud Services (extended support) roles.
 
     ```azurepowershell-interactive
     $Policy = New-AzKeyVaultCertificatePolicy -SecretContentType "application/x-pkcs12" -SubjectName "CN=contoso.com" -IssuerName "Self" -ValidityInMonths 6 -ReuseKeyOnRenewal 
@@ -223,7 +223,7 @@ New-AzCloudService
     $tag=@{"Owner" = "Contoso"} 
     ```
 
-1. Create the Cloud Service (extended support) deployment by using the profile objects and SAS URIs that you defined:
+1. Create the Cloud Services (extended support) deployment by using the profile objects and SAS URIs that you defined:
 
     ```azurepowershell-interactive
     $cloudService = New-AzCloudService ` 

articles/cloud-services-extended-support/deploy-prerequisite.md

@@ -13,16 +13,18 @@ ms.date: 06/16/2024
 
 To help ensure a successful Azure Cloud Services (extended support) deployment, review the following steps. Complete each prerequisitive before you begin to create a deployment.
 
-## Required service configuration (.cscfg) file updates
+## Required configuration (.cscfg) file updates
+
+Use the information in the following sections to make required updates to the configuration (.cscfg) file for your Cloud Services (extended support) deployment.
 
 ### Virtual network
 
-Cloud Services (extended support) deployments must be in a virtual network. You can create a virtual network by using the [Azure portal](../virtual-network/quick-create-portal.md), [Azure PowerShell](../virtual-network/quick-create-powershell.md), the [Azure CLI](../virtual-network/quick-create-cli.md), or an [Azure Resource Manager template (ARM template)](../virtual-network/quick-create-template.md). The virtual network and subnets must be referenced in the [NetworkConfiguration](schema-cscfg-networkconfiguration.md) section of the .cscfg file.
+Cloud Services (extended support) deployments must be in a virtual network. You can create a virtual network by using the [Azure portal](../virtual-network/quick-create-portal.md), [Azure PowerShell](../virtual-network/quick-create-powershell.md), the [Azure CLI](../virtual-network/quick-create-cli.md), or an [Azure Resource Manager template (ARM template)](../virtual-network/quick-create-template.md). The virtual network and subnets must be referenced in the [NetworkConfiguration](schema-cscfg-networkconfiguration.md) section of the configuration (.cscfg) file.
 
-For a virtual network that is in the same resource group as the cloud service, referencing only the virtual network name in the .cscfg file is sufficient. If the virtual network and cloud service are in two different resource groups, specify the complete Azure Resource Manager ID of the virtual network in the .cscfg file.
+For a virtual network that is in the same resource group as the cloud service, referencing only the virtual network name in the configuration (.cscfg) file is sufficient. If the virtual network and Cloud Services (extended support) are in two different resource groups, specify the complete Azure Resource Manager ID of the virtual network in the configuration (.cscfg) file.
 
 > [!NOTE]
-> If the virtual network and cloud service are located in different resource groups, you can't use Visual Studio 2019 for your deployment. For this scenario, consider using an ARM template or the Azure portal to create your deployment.
+> If the virtual network and Cloud Services (extended support) are located in different resource groups, you can't use Visual Studio 2019 for your deployment. For this scenario, consider using an ARM template or the Azure portal to create your deployment.
 
 #### Virtual network in the same resource group
 
@@ -52,7 +54,7 @@ For a virtual network that is in the same resource group as the cloud service, r
 
 ### Remove earlier versions of plugins
 
-Remove earlier versions of remote desktop settings from the .cscfg file:
+Remove earlier versions of remote desktop settings from the configuration (.cscfg) file:
 
 ```xml
 <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" /> 
@@ -62,16 +64,16 @@ Remove earlier versions of remote desktop settings from the .cscfg file:
 <Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" /> 
 ```
 
-Remove earlier versions of diagnostics settings for each role in the .cscfg file:
+Remove earlier versions of diagnostics settings for each role in the configuration (.cscfg) file:
 
 ```xml
 <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="UseDevelopmentStorage=true" />
 ```
 
-## Required service definition file updates
+## Required definition file updates
 
 > [!NOTE]
-> If you make changes to the service definition (.csdef) file, you must generate the package (.cspkg) file again. Build and repackage your .cspkg file after you make the following changes in the .csdef file to get the latest settings for your cloud service.
+> If you make changes to the definition (.csdef) file, you must generate the package (.cspkg or .zip) file again. Build and repackage your package (.cspkg or .zip) file after you make the following changes in the definition (.csdef) file to get the latest settings for your cloud service.
 
 ### Virtual machine sizes
 
@@ -105,7 +107,7 @@ For example, `<WorkerRole name="WorkerRole1" vmsize="Medium">` becomes `<WorkerR
 
 ### Remove earlier versions of remote desktop plugins
 
-For deployments that use earlier versions of remote desktop plugins, remove the modules from the .csdef file and from any associated certificates:
+For deployments that use earlier versions of remote desktop plugins, remove the modules from the definition (.csdef) file and from any associated certificates:
 
 ```xml
 <Imports> 
@@ -114,19 +116,19 @@ For deployments that use earlier versions of remote desktop plugins, remove the
 </Imports> 
 ```
 
-For deployments that use earlier versions of diagnostics plugins, remove the settings for each role from the .csdef file:
+For deployments that use earlier versions of diagnostics plugins, remove the settings for each role from the definition (.csdef) file:
 
 ```xml
 <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" />
 ```
 
 ## Access control
 
-The subscription that contains networking resources must have [Network Contributor](../role-based-access-control/built-in-roles.md#network-contributor) or greater access for Cloud Services (extended support). For more information, see [RBAC built-in roles](../role-based-access-control/built-in-roles.md).
+The subscription that contains networking resources must have the [Network Contributor](../role-based-access-control/built-in-roles.md#network-contributor) or greater role for Cloud Services (extended support). For more information, see [RBAC built-in roles](../role-based-access-control/built-in-roles.md).
 
 ## Key vault creation
 
-Azure Key Vault is used to store certificates that are associated with Cloud Services (extended support). Add the certificates to Key Vault, and then reference the certificate thumbprints in your service configuration file. You also must enable the Key Vault access policy (in the portal) for *Azure Virtual Machines for deployment* so that the Cloud Services (extended support) resource can retrieve the certificate that's stored as secrets from Key Vault. You can create a key vault in the [Azure portal](../key-vault/general/quick-create-portal.md) or by using [PowerShell](../key-vault/general/quick-create-powershell.md). You must create the key vault in the same region and subscription as the cloud service. For more information, see [Use certificates with Azure Cloud Services (extended support)](certificates-and-key-vault.md).
+Azure Key Vault stores certificates that are associated with Cloud Services (extended support). Add the certificates to a key vault, and then reference the certificate thumbprints in the configuration (.cscfg) file for your deployment. You also must enable the key vault access policy (in the portal) for **Azure Virtual Machines for deployment** so that the Cloud Services (extended support) resource can retrieve the certificate that's stored as secrets in the key vault. You can create a key vault in the [Azure portal](../key-vault/general/quick-create-portal.md) or by using [PowerShell](../key-vault/general/quick-create-powershell.md). You must create the key vault in the same region and subscription as the cloud service. For more information, see [Use certificates with Cloud Services (extended support)](certificates-and-key-vault.md).
 
 ## Related content