You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/ResourceManager/ApiManagement/Commands.ApiManagement.ServiceManagement/Microsoft.Azure.Commands.ApiManagement.ServiceManagement.dll-help.xml
Copy file name to clipboardExpand all lines: src/ResourceManager/ApiManagement/Commands.ApiManagement/Microsoft.Azure.Commands.ApiManagement.dll-help.xml
Copy file name to clipboardExpand all lines: src/ResourceManager/Automation/Commands.Automation/Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.xml
<maml:para>Specifies the name of an existing resource group. In order to create a resource group, use the New-AzureResourceGroup commandlet. There is no requirement that the Azure ResourceGroup and the Azure Backup vault be in the same region.</maml:para>
3127
+
<maml:para>Specifies the name of an existing resource group. In order to create a resource group, use the New-AzureRMResourceGroup commandlet. There is no requirement that the Azure ResourceGroup and the Azure Backup vault be in the same region.</maml:para>
<maml:para>Specifies the name of an existing resource group. In order to create a resource group, use the New-AzureResourceGroup commandlet. There is no requirement that the Azure ResourceGroup and the Azure Backup vault be in the same region.</maml:para>
3165
+
<maml:para>Specifies the name of an existing resource group. In order to create a resource group, use the New-AzureRMResourceGroup commandlet. There is no requirement that the Azure ResourceGroup and the Azure Backup vault be in the same region.</maml:para>
<maml:para>The cloud service name of the Azure VM to be registered. Typically the cloud service name has a suffix ".cloudapp.net". Do not include the suffix as input to this commandlet! You can use the Get-AzureVM commandlet (in the AzureServiceManagement mode) to get the VM information; the service name is the DeploymentName property in the VM object.</maml:para>
3356
+
<maml:para>The cloud service name of the Azure VM to be registered. Typically the cloud service name has a suffix ".cloudapp.net". Do not include the suffix as input to this commandlet! You can use the Get-AzureRMVM commandlet (in the AzureServiceManagement mode) to get the VM information; the service name is the DeploymentName property in the VM object.</maml:para>
<maml:para>The cloud service name of the Azure VM to be registered. Typically the cloud service name has a suffix ".cloudapp.net". Do not include the suffix as input to this commandlet! You can use the Get-AzureVM commandlet (in the AzureServiceManagement mode) to get the VM information; the service name is the DeploymentName property in the VM object.</maml:para>
3423
+
<maml:para>The cloud service name of the Azure VM to be registered. Typically the cloud service name has a suffix ".cloudapp.net". Do not include the suffix as input to this commandlet! You can use the Get-AzureRMVM commandlet (in the AzureServiceManagement mode) to get the VM information; the service name is the DeploymentName property in the VM object.</maml:para>
<maml:para>The Remove-AzureBackupVault commandlet deletes the backup vault. However, before a vault can be removed, it must first be empty – it must contain no backup data or protected items or registered servers. This ensures that a vault cannot be deleted inadvertently; the deletion of a backup vault is a planned operation.</maml:para>
3676
-
<maml:para>Use the Remove-AzureBackupContainer commandlet to clear up IaaS VM backup data from the vault, or use the Delete-RegisteredServer commandlet to clear up other registered servers and backup data.</maml:para>
3675
+
<maml:para>The Remove-AzureRMBackupVault commandlet deletes the backup vault. However, before a vault can be removed, it must first be empty – it must contain no backup data or protected items or registered servers. This ensures that a vault cannot be deleted inadvertently; the deletion of a backup vault is a planned operation.</maml:para>
3676
+
<maml:para>Use the Remove-AzureRMBackupContainer commandlet to clear up IaaS VM backup data from the vault, or use the Delete-RegisteredServer commandlet to clear up other registered servers and backup data.</maml:para>
<maml:para>The Set-AzureBackupVault commandlet allows you to change the storage type of the backup vault. The other parameters like Region, Name, and ResourceGroupName are not editable.</maml:para>
4252
+
<maml:para>The Set-AzureRMBackupVault commandlet allows you to change the storage type of the backup vault. The other parameters like Region, Name, and ResourceGroupName are not editable.</maml:para>
<maml:para>The user first gets the container that needs to be unregistered using the Get-AzureBackupContainer commandlet. This container object is passed to the unregister commandlet. This unregisters the specified Windows Server from the Azure Backup vault.</maml:para>
4702
+
<maml:para>The user first gets the container that needs to be unregistered using the Get-AzureRMBackupContainer commandlet. This container object is passed to the unregister commandlet. This unregisters the specified Windows Server from the Azure Backup vault.</maml:para>
4703
4703
<maml:para />
4704
4704
<maml:para />
4705
4705
<maml:para>Unregister Server
@@ -4719,7 +4719,7 @@ This operation will delete all data in the backup vault that is associated with
0 commit comments