DeploymentOperationsExtensions Class

The Abort Deployment Operation validates and aborts your deployment for IaaS Classic to ARM migration.

The Abort Deployment Operation validates and aborts your deployment for IaaS Classic to ARM migration.

The Abort Deployment Operation validates and aborts your deployment for IaaS Classic to ARM migration.

The Abort Deployment Operation validates and aborts your deployment for IaaS Classic to ARM migration.

The Begin Changing Deployment Configuration By Name operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Begin Changing Deployment Configuration By Name operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Begin Changing Deployment Configuration By Slot operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Begin Changing Deployment Configuration By Slot operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Commit Deployment Operation validates and commits your deployment for IaaS Classic to ARM migration.

The Commit Deployment Operation validates and commits your deployment for IaaS Classic to ARM migration.

The Begin Creating Deployment operation uploads a new service package and creates a new deployment in the staging or production environments. This operation is an asynchronous operation. To determine whether the management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460813.aspx for more information)

The Begin Creating Deployment operation uploads a new service package and creates a new deployment in the staging or production environments. This operation is an asynchronous operation. To determine whether the management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460813.aspx for more information)

The Begin Deleting Deployment By Name operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Begin Deleting Deployment By Name operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Begin Deleting Deployment By Slot operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Begin Deleting Deployment By Slot operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Delete Role Instances operation deletes a role instance from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Delete Role Instances operation deletes a role instance from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Delete Role Instances operation deletes a role instance from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Delete Role Instances operation deletes a role instance from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Get Package By Name operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Get Package By Name operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Get Package By Slot operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Get Package By Slot operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Prepare Deployment Operation validates and prepares your deployment for IaaS Classic to ARM migration.

The Prepare Deployment Operation validates and prepares your deployment for IaaS Classic to ARM migration.

The Begin Rebooting Role Instance By Deployment Name operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Begin Rebooting Role Instance By Deployment Name operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Begin Rebooting Role Instance By Deployment Slot operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Begin Rebooting Role Instance By Deployment Slot operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Begin Reimaging Role Instance By Deployment Name operation requests a reimage of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Begin Reimaging Role Instance By Deployment Name operation requests a reimage of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Begin Reimaging Role Instance By Deployment Slot operation requests a reimage of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Begin Reimaging Role Instance By Deployment Slot operation requests a reimage of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Begin Swapping Deployment operation initiates a virtual IP address swap between the staging and production deployment environments for a service. If the service is currently running in the staging environment, it will be swapped to the production environment. If it is running in the production environment, it will be swapped to staging. For more information on this type of upgrade, see Performing Virtual IP Swap Upgrades at http://msdn.microsoft.com/en-us/library/windowsazure/ee517253.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460814.aspx for more information)

The Begin Swapping Deployment operation initiates a virtual IP address swap between the staging and production deployment environments for a service. If the service is currently running in the staging environment, it will be swapped to the production environment. If it is running in the production environment, it will be swapped to staging. For more information on this type of upgrade, see Performing Virtual IP Swap Upgrades at http://msdn.microsoft.com/en-us/library/windowsazure/ee517253.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460814.aspx for more information)

The Begin Updating Deployment Status By Deployment Name operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Begin Updating Deployment Status By Deployment Name operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Begin Updating Deployment Status By Deployment Slot operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Begin Updating Deployment Status By Deployment Slot operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Begin Upgrading Deployment By Name operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Begin Upgrading Deployment By Name operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Begin Upgrading Deployment By Slot operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx.This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Begin Upgrading Deployment By Slot operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx.This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Begin Walking Upgrade Domain By Deployment Name operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Begin Walking Upgrade Domain By Deployment Name operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Begin Walking Upgrade Domain By Deployment Slot operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Begin Walking Upgrade Domain By Deployment Slot operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Change Deployment Configuration By Name operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Change Deployment Configuration By Name operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Change Deployment Configuration By Slot operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Change Deployment Configuration By Slot operation initiates a change to the deployment configuration. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460809.aspx for more information)

The Commit Deployment Operation validates and commits your deployment for IaaS Classic to ARM migration.

The Commit Deployment Operation validates and commits your deployment for IaaS Classic to ARM migration.

The Create Deployment operation uploads a new service package and creates a new deployment in the staging or production environments. This operation is an asynchronous operation. To determine whether the management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460813.aspx for more information)

The Create Deployment operation uploads a new service package and creates a new deployment in the staging or production environments. This operation is an asynchronous operation. To determine whether the management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460813.aspx for more information)

The Delete Deployment By Name operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Delete Deployment By Name operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Delete Deployment By Slot operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Delete Deployment By Slot operation deletes the specified deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460815.aspx for more information)

The Delete Role Instances operation deletes a role instance from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Delete Role Instances operation deletes a role instance from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Delete Role Instances operation deletes the role instances from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Delete Role Instances operation deletes the role instances from a deployment in a cloud service. (see http://msdn.microsoft.com/en-us/library/windowsazure/dn469418.aspx for more information)

The Get Deployment By Name operation returns configuration information, status, and system properties for a deployment. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460804.aspx for more information)

The Get Deployment By Name operation returns configuration information, status, and system properties for a deployment. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460804.aspx for more information)

The Get Deployment By Slot operation returns configuration information, status, and system properties for a deployment. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460804.aspx for more information)

The Get Deployment By Slot operation returns configuration information, status, and system properties for a deployment. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460804.aspx for more information)

The Get Package By Name operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Get Package By Name operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Get Package By Slot operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

The Get Package By Slot operation retrieves a cloud service package for a deployment and stores the package files in Azure Blob storage. The following package files are placed in storage: the cloud service configuration file (.cscfg), providing configuration settings for the cloud service and individual roles, including the number of role instances; and the service package (.cspkg), containing the application code and the service definition file. (see http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx for more information)

Identifies the list of reboot events due to planned maintenance that impacted a deployment in the optionally provided timeframe.

Identifies the list of reboot events due to planned maintenance that impacted a deployment in the optionally provided timeframe.

Identifies the list of reboot events due to planned maintenance that impacted a deployment in the optionally provided timeframe.

Identifies the list of reboot events due to planned maintenance that impacted a deployment in the optionally provided timeframe.

The Prepare Deployment Operation validates and prepares your deployment for IaaS Classic to ARM migration.

The Prepare Deployment Operation validates and prepares your deployment for IaaS Classic to ARM migration.

The Reboot Role Instance By Deployment Name operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Reboot Role Instance By Deployment Name operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Reboot Role Instance By Deployment Slot operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Reboot Role Instance By Deployment Slot operation requests a reboot of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441298.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance athttp://msdn.microsoft.com/en-us/library/azure/gg441292.aspx.For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/azure/dn627518.aspx for more information)

The Reimage Role Instance By Deployment Name operation requests a reimage of a role instance that is running in a deployment.This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Reimage Role Instance By Deployment Name operation requests a reimage of a role instance that is running in a deployment.This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Reimage Role Instance By Deployment Slot operation requests a reimage of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Reimage Role Instance By Deployment Slot operation requests a reimage of a role instance that is running in a deployment. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/gg441292.aspx for more information)

The Rollback Update Or Upgrade By Deployment Name operation cancels an in-progress configuration update and returns the deployment to its state before the update was started. This operation can only be called when an update is in progress on the deployment. The deployment status can be detected by calling the Get Deployment operation or Get Hosted Service Properties operation and inspecting the RollbackAllowed element. If the value returned is true a rollback can be performed. (see http://msdn.microsoft.com/en-us/library/windowsazure/hh403977.aspx for more information)

The Rollback Update Or Upgrade By Deployment Name operation cancels an in-progress configuration update and returns the deployment to its state before the update was started. This operation can only be called when an update is in progress on the deployment. The deployment status can be detected by calling the Get Deployment operation or Get Hosted Service Properties operation and inspecting the RollbackAllowed element. If the value returned is true a rollback can be performed. (see http://msdn.microsoft.com/en-us/library/windowsazure/hh403977.aspx for more information)

The Rollback Update Or Upgrade By Deployment Slot operation cancels an in-progress configuration update and returns the deployment to its state before the update was started. This operation can only be called when an update is in progress on the deployment. The deployment status can be detected by calling the Get Deployment operation or Get Hosted Service Properties operation and inspecting the RollbackAllowed element. If the value returned is true a rollback can be performed. (see http://msdn.microsoft.com/en-us/library/windowsazure/hh403977.aspx for more information)

The Rollback Update Or Upgrade By Deployment Slot operation cancels an in-progress configuration update and returns the deployment to its state before the update was started. This operation can only be called when an update is in progress on the deployment. The deployment status can be detected by calling the Get Deployment operation or Get Hosted Service Properties operation and inspecting the RollbackAllowed element. If the value returned is true a rollback can be performed. (see http://msdn.microsoft.com/en-us/library/windowsazure/hh403977.aspx for more information)

The Swap Deployment operation initiates a virtual IP address swap between the staging and production deployment environments for a service. If the service is currently running in the staging environment, it will be swapped to the production environment. If it is running in the production environment, it will be swapped to staging. For more information on this type of upgrade, see Performing Virtual IP Swap Upgrades at http://msdn.microsoft.com/en-us/library/windowsazure/ee517253.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460814.aspx for more information)

The Swap Deployment operation initiates a virtual IP address swap between the staging and production deployment environments for a service. If the service is currently running in the staging environment, it will be swapped to the production environment. If it is running in the production environment, it will be swapped to staging. For more information on this type of upgrade, see Performing Virtual IP Swap Upgrades at http://msdn.microsoft.com/en-us/library/windowsazure/ee517253.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460814.aspx for more information)

The Update Deployment Status By Deployment Name operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Update Deployment Status By Deployment Name operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Update Deployment Status By Deployment Slot operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Update Deployment Status By Deployment Slot operation initiates a change in the running status of a deployment. The status of a deployment can be running or suspended. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460808.aspx for more information)

The Upgrade Deployment By Name operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Upgrade Deployment By Name operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Upgrade Deployment By Slot operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Upgrade Deployment By Slot operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)

The Validate Deployment Operation validates your deployment for IaaS Classic to ARM migration.

The Validate Deployment Operation validates your deployment for IaaS Classic to ARM migration.

The Walk Upgrade Domain By Deployment Name operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Walk Upgrade Domain By Deployment Name operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Walk Upgrade Domain By Deployment Slot operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)

The Walk Upgrade Domain By Deployment Slot operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)