Merge pull request #281732 from tomvcassidy/37CSDate

ms.date and acrolinx for twelve articles

Author: JamesJBarnett

articles/cloud-services-extended-support/available-sizes.md

@@ -6,7 +6,7 @@ ms.service: cloud-services-extended-support
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 10/13/2020
+ms.date: 07/24/2024
 ---
 
 # Available sizes for Azure Cloud Services (extended support)
@@ -32,7 +32,7 @@ This article describes the available virtual machine sizes for Cloud Services (e
 
 ## Configure sizes for Cloud Services (extended support)
 
-You can specify the virtual machine size of a role instance as part of the service model in the service definition file. The size of the role determines the number of CPU cores, memory capacity and the local file system size.
+You can specify the virtual machine size of a role instance as part of the service model in the service definition file. The size of the role determines the number of CPU cores, memory capacity, and the local file system size.
 
 For example, setting the web role instance size to `Standard_D2`: 
 
@@ -49,7 +49,7 @@ To change the size of an existing role, change the virtual machine size in the s
 
 ## Get a list of available sizes 
 
-To retrieve a list of available sizes see [Resource Skus - List](/rest/api/compute/resourceskus/list) and apply the following filters:
+To retrieve a list of available sizes, see [Resource Skus - List](/rest/api/compute/resourceskus/list) and apply the following filters:
 
 ```powershell
     # Update the location

articles/cloud-services-extended-support/certificates-and-key-vault.md

@@ -6,7 +6,7 @@ ms.service: cloud-services-extended-support
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 10/13/2020
+ms.date: 07/24/2024
 ---
 
 # Use certificates with Azure Cloud Services (extended support)
@@ -15,13 +15,13 @@ Key Vault is used to store certificates that are associated to Cloud Services (e
 
 ## Upload a certificate to Key Vault 
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to the Key Vault. If you do not have a Key Vault set up, you can opt to create one in this same window.
+1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to the Key Vault. If you don't have a Key Vault set up, you can opt to create one in this same window.
 
 2. Select **Access Configuration**
 
     :::image type="content" source="media/certs-and-key-vault-1.png" alt-text="Image shows selecting access policies from the key vault blade.":::
 
-3. Ensure the access configuration include the following property:
+3. Ensure the access configuration includes the following property:
     - **Enable access to Azure Virtual Machines for deployment**
 
     :::image type="content" source="media/certs-and-key-vault-2.png" alt-text="Image shows access policies window in the Azure portal.":::

articles/cloud-services-extended-support/cloud-services-model-and-package.md

@@ -6,14 +6,14 @@ ms.service: cloud-services-extended-support
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 10/13/2020
+ms.date: 07/24/2024
 ---
 
 # What is the Azure Cloud Service model and how do I package it?
 
-A cloud service is created from three components, the service definition *(.csdef)*, the service config *(.cscfg)*, and a service package *(.cspkg)*. Both the **ServiceDefinition.csdef** and **ServiceConfig.cscfg** files are XML-based and describe the structure of the cloud service and how it's configured; collectively called the model. The **ServicePackage.cspkg** is a zip file that is generated from the **ServiceDefinition.csdef** and among other things, contains all the required binary-based dependencies. Azure creates a cloud service from both the **ServicePackage.cspkg** and the **ServiceConfig.cscfg**.
+A cloud service is created from three components, the service definition *(.csdef)*, the service config *(.cscfg)*, and a service package *(.cspkg)*. Both the **ServiceDefinition.csdef** and **ServiceConfig.cscfg** files are XML-based and describe the structure of the cloud service and its configuration. We collectively call these files the model. The **ServicePackage.cspkg** is a zip file that is generated from the **ServiceDefinition.csdef** and among other things, contains all the required binary-based dependencies. Azure creates a cloud service from both the **ServicePackage.cspkg** and the **ServiceConfig.cscfg**.
 
-Once the cloud service is running in Azure, you can reconfigure it through the **ServiceConfig.cscfg** file, but you cannot alter the definition.
+Once the cloud service is running in Azure, you can reconfigure it through the **ServiceConfig.cscfg** file, but you can't alter the definition.
 
 ## What would you like to know more about?
 * I want to know more about the [ServiceDefinition.csdef](#csdef) and [ServiceConfig.cscfg](#cscfg) files.
@@ -74,7 +74,7 @@ The **ServiceDefinition.csdef** file specifies the settings that are used by Azu
 </ServiceDefinition>
 ```
 
-You can refer to the [Service Definition Schema](schema-csdef-file.md)) for a better understanding of the XML schema used here, however, here is a quick explanation of some of the elements:
+You can refer to the [Service Definition Schema](schema-csdef-file.md)) for a better understanding of the XML schema used here, however, here's a quick explanation of some of the elements:
 
 **Sites**  
 Contains the definitions for websites or web applications that are hosted in IIS7.
@@ -105,7 +105,7 @@ Contains tasks that are run when the role starts. The tasks are defined in a .cm
 ## ServiceConfiguration.cscfg
 The configuration of the settings for your cloud service is determined by the values in the **ServiceConfiguration.cscfg** file. You specify the number of instances that you want to deploy for each role in this file. The values for the configuration settings that you defined in the service definition file are added to the service configuration file. The thumbprints for any management certificates that are associated with the cloud service are also added to the file. The [Azure Service Configuration Schema (.cscfg File)](schema-cscfg-file.md) provides the allowable format for a service configuration file.
 
-The service configuration file is not packaged with the application, but is uploaded to Azure as a separate file and is used to configure the cloud service. You can upload a new service configuration file without redeploying your cloud service. The configuration values for the cloud service can be changed while the cloud service is running. The following example shows the configuration settings that can be defined for the Web and Worker roles:
+The service configuration file isn't packaged with the application. It uploads to Azure as a separate file and is used to configure the cloud service. You can upload a new service configuration file without redeploying your cloud service. The configuration values for the cloud service can be changed while the cloud service is running. The following example shows the configuration settings that can be defined for the Web and Worker roles:
 
 ```xml
 <?xml version="1.0"?>
@@ -125,10 +125,10 @@ The service configuration file is not packaged with the application, but is uplo
 </ServiceConfiguration>
 ```
 
-You can refer to the [Service Configuration Schema](schema-cscfg-file.md) for better understanding the XML schema used here, however, here is a quick explanation of the elements:
+You can refer to the [Service Configuration Schema](schema-cscfg-file.md) for better understanding the XML schema used here, however, here's a quick explanation of the elements:
 
 **Instances**  
-Configures the number of running instances for the role. To prevent your cloud service from potentially becoming unavailable during upgrades, it is recommended that you deploy more than one instance of your web-facing roles. By deploying more than one instance, you are adhering to the guidelines in the [Azure Compute Service Level Agreement (SLA)](https://azure.microsoft.com/support/legal/sla/), which guarantees 99.95% external connectivity for Internet-facing roles when two or more role instances are deployed for a service.
+Configures the number of running instances for the role. To prevent your cloud service from potentially becoming unavailable during upgrades, we recommend you deploy more than one instance of your web-facing roles. By deploying more than one instance, you adhere to the guidelines in the [Azure Compute Service Level Agreement (SLA)](https://azure.microsoft.com/support/legal/sla/), which guarantees 99.95% external connectivity for Internet-facing roles when two or more role instances are deployed for a service.
 
 **ConfigurationSettings**  
 Configures the settings for the running instances for a role. The name of the `<Setting>` elements must match the setting definitions in the service definition file.
@@ -146,7 +146,7 @@ Configures the certificates that are used by the service. The previous code exam
 ## Defining ports for role instances
 Azure allows only one entry point to a web role. Meaning that all traffic occurs through one IP address. You can configure your websites to share a port by configuring the host header to direct the request to the correct location. You can also configure your applications to listen to well-known ports on the IP address.
 
-The following sample shows the configuration for a web role with a website and web application. The website is configured as the default entry location on port 80, and the web applications are configured to receive requests from an alternate host header that is called “mail.mysite.cloudapp.net”.
+The following sample shows the configuration for a web role with a website and web application. The website is configured as the default entry location on port 80, and the web applications are configured to receive requests from an alternate host header called `mail.mysite.cloudapp.net`.
 
 ```xml
 <WebRole>
@@ -182,14 +182,14 @@ The following sample shows the configuration for a web role with a website and w
 
 
 ## Changing the configuration of a role
-You can update the configuration of your cloud service while it is running in Azure, without taking the service offline. To change configuration information, you can either upload a new configuration file, or edit the configuration file in place and apply it to your running service. The following changes can be made to the configuration of a service:
+You can update the configuration of your cloud service while it's running in Azure, without taking the service offline. To change configuration information, you can either upload a new configuration file, or edit the configuration file in place and apply it to your running service. The following changes can be made to the configuration of a service:
 
 * **Changing the values of configuration settings**  
   When a configuration setting changes, a role instance can choose to apply the change while the instance is online, or to recycle the instance gracefully and apply the change while the instance is offline.
 * **Changing the service topology of role instances**  
-  Topology changes do not affect running instances, except where an instance is being removed. All remaining instances generally do not need to be recycled; however, you can choose to recycle role instances in response to a topology change.
+  Topology changes don't affect running instances, except where an instance is being removed. All remaining instances generally don't need to be recycled; however, you can choose to recycle role instances in response to a topology change.
 * **Changing the certificate thumbprint**  
-  You can only update a certificate when a role instance is offline. If a certificate is added, deleted, or changed while a role instance is online, Azure gracefully takes the instance offline to update the certificate and bring it back online after the change is complete.
+  You can only update a certificate when a role instance is offline. If a certificate is added, deleted, or changed while a role instance is online, Azure gracefully takes the instance offline to update the certificate. Azure brings it back online after the change completes.
 
 ### Handling configuration changes with Service Runtime Events
 The Azure Runtime Library includes the Microsoft.WindowsAzure.ServiceRuntime namespace, which provides classes for interacting with the Azure environment from a role. The RoleEnvironment class defines the following events that are raised before and after a configuration change:
@@ -256,7 +256,7 @@ Where the variables are defined as follows:
 | --- | --- |
 | \[DirectoryName\] |The subdirectory under the root project directory that contains the .csdef file of the Azure project. |
 | \[ServiceDefinition\] |The name of the service definition file. By default, this file is named ServiceDefinition.csdef. |
-| \[OutputFileName\] |The name for the generated package file. Typically, this is set to the name of the application. If no file name is specified, the application package is created as \[ApplicationName\].cspkg. |
+| \[OutputFileName\] |The name for the generated package file. Typically, this variable is set to the name of the application. If no file name is specified, the application package is created as \[ApplicationName\].cspkg. |
 | \[RoleName\] |The name of the role as defined in the service definition file. |
 | \[RoleBinariesDirectory] |The location of the binary files for the role. |
 | \[VirtualPath\] |The physical directories for each virtual path defined in the Sites section of the service definition. |

articles/cloud-services-extended-support/configure-scaling.md

@@ -7,12 +7,12 @@ ms.subservice: autoscale
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 10/13/2020
+ms.date: 07/24/2024
 ---
 
 # Configure scaling options with Azure Cloud Services (extended support) 
 
-Conditions can be configured to enable Cloud Services (extended support) deployments to scale in and out. These conditions can be based on CPU usage, disk load and network load. 
+Conditions can be configured to enable Cloud Services (extended support) deployments to scale in and out. These conditions can be based on CPU usage, disk load, and network load. 
 
 Consider the following information when configuring scaling of your Cloud Service deployments:
 - Scaling impacts core usage. Larger role instances consume more cores and you can only scale within the core limit of your subscription. For more information, see [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md).
@@ -28,18 +28,18 @@ Consider the following information when configuring scaling of your Cloud Servic
 
 	:::image type="content" source="media/enable-scaling-1.png" alt-text="Image shows selecting the Remote Desktop option in the Azure portal":::
 
-4. A page will display a list of all the roles in which scaling can be configured. Select the role you want to configure. 
+4. A page displays a list of all the roles in which scaling can be configured. Select the role you want to configure. 
 5. Select the type of scale you want to configure
-	- **Manual scale** will set the absolute count of instances.
+	- **Manual scale** sets the absolute count of instances.
 		1. Select **Manual scale**.
 		2. Input the number of instances you want to scale up or down to.
 		3. Select **Save**.
 
 		:::image type="content" source="media/enable-scaling-2.png" alt-text="Image shows setting up manual scaling in the Azure portal":::
 
-		4. The scaling operation will begin immediately. 
+		4. The scaling operation begins immediately. 
 		
-	- **Custom Autoscale** will allow you to set rules that govern how much or how little to scale. 
+	- **Custom Autoscale** allows you to set rules that govern how much or how little to scale. 
 		1. Select **Custom autoscale**
 		2. Choose to scale based on a metric or instance count.
 
@@ -50,7 +50,7 @@ Consider the following information when configuring scaling of your Cloud Servic
 		:::image type="content" source="media/enable-scaling-4.png" alt-text="Image shows setting up custom autoscale rules in the Azure portal":::
 
 		4. Select **Save**.
-		5. The scaling operations will begin as soon as a rule is triggered.
+		5. The scaling operations begin as soon as a rule is triggered.
 		
 6. You can view or adjust existing scaling rules applied to your deployments by selecting the **Scale** tab.
 

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

@@ -6,7 +6,7 @@ ms.service: cloud-services-extended-support
 author: gachandw
 ms.author: gachandw
 ms.reviewer: mimckitt
-ms.date: 06/18/2024
+ms.date: 07/24/2024
 ---
 
 # Deploy Cloud Services (extended support) by using the Azure portal
@@ -59,8 +59,8 @@ To deploy Cloud Services (extended support) by using the portal:
         - If you have IP input endpoints defined in your definition (.csdef) file, create a public IP address for your cloud service.
         - Cloud Services (extended support) supports only a Basic SKU public IP address.
         - If your configuration (.cscfg) file contains a reserved IP address, set the allocation type for the public IP address to **Static**.
-        - (Optional) You can assign a DNS name for your cloud service endpoint by updating the DNS label property of the public IP address that's associated with the cloud service.  
-    - (Optional) **Start cloud service**: Select the checkbox if you want to start the service immediately after it's deployed.
+        - (Optional) You can assign a DNS name for your cloud service endpoint by updating the DNS label property of the public IP address associated with the cloud service.  
+    - (Optional) **Start cloud service**: Select the checkbox if you want to start the service immediately after it deploys.
     - **Key vault**: Select a key vault.
         - A key vault is required when you specify one or more certificates in your configuration (.cscfg) file. When you select a key vault, we attempt to find the selected certificates that are defined in your configuration (.cscfg) file based on the certificate thumbprints. If any certificates are missing from your key vault, you can upload them now    , and then select **Refresh**.