Skip to content

Commit

Permalink
Updated upcoming breaking changes with new format
Browse files Browse the repository at this point in the history
  • Loading branch information
mikefrobbins committed Jun 29, 2023
1 parent 6a50011 commit 04bc8f8
Showing 1 changed file with 86 additions and 8 deletions.
94 changes: 86 additions & 8 deletions docs-conceptual/azps-10.0.0/upcoming-breaking-changes.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Learn about upcoming breaking changes to the Azure Az PowerShell module
ms.custom: devx-track-azurepowershell
ms.date: 06/09/2023
ms.date: 06/29/2023
ms.devlang: powershell
ms.service: azure-powershell
ms.topic: conceptual
Expand All @@ -14,28 +14,36 @@ title: Upcoming breaking changes in Azure PowerShell

### `New-AzAksCluster`

- The `-DockerBridgeCidr` parameter will be deprecated in Az 11.0.0 without being replaced.
- Parameter breaking-change will happen to all parameter sets
- `-DockerBridgeCidr`
- DockerBridgeCidr parameter will be deprecated in Az 11.0.0 without being replaced.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

## Az.Compute

### `New-AzDisk`

- Cmdlet breaking-change will happen to all parameter set
- Starting in November 2023 the "New-AzDisk" cmdlet will deploy with the Trusted Launch configuration by default. This includes defaulting the "HyperVGeneration" parameter to "v2". To know more about Trusted Launch, please visit [learn.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch)
- Starting in November 2023 the "New-AzDisk" cmdlet will deploy with the Trusted Launch configuration by default. This includes defaulting the "HyperVGeneration" parameter to "v2". To know more about Trusted Launch, please visit [docs.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch)
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0

### `New-AzVM`

- Cmdlet breaking-change will happen to all parameter set
- Consider using the image alias including the version of the distribution you want to use in the "-Image" parameter of the "New-AzVM" cmdlet. On April 30, 2023, the image deployed using `UbuntuLTS` will reach its end of life. In October 2023, the aliases `UbuntuLTS`, `CentOS`, `Debian`, and `RHEL` will be removed.
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0
- Starting in November 2023 the "New-AzVM" cmdlet will deploy with the Trusted Launch configuration by default. To know more about Trusted Launch, please visit [docs.microsoft.com/azure/virtual-machines/trusted-launch](/azure/virtual-machines/trusted-launch)
- It is recommended to use parameter "-PublicIpSku Standard" in order to create a new VM with a Standard public IP.Specifying zone(s) using the "-Zone" parameter will also result in a Standard public IP.If "-Zone" and "-PublicIpSku" are not specified, the VM will be created with a Basic public IP instead.Please note that the Standard SKU IPs will become the default behavior for VM creation in the future
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0

### `New-AzVmss`

- Cmdlet breaking-change will happen to all parameter set
- Starting November 2023, the "New-AzVmss" cmdlet will default to Trusted Launch VMSS. For more info, visit [aka.ms/trustedLaunchVMSS](https://aka.ms/trustedLaunchVMSS).
- Starting November 2023, the "New-AzVmss" cmdlet will use new defaults: Flexible orchestration mode and enable NATv2 configuration for Load Balancer. To learn more about Flexible Orchestration modes, visit [aka.ms/orchestrationModeVMSS](https://aka.ms/orchestrationModeVMSS).
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0
- Starting November 2023, the "New-AzVmss" cmdlet will use new defaults: Flexible orchestration mode and enable NATv2 configuration for Load Balancer. To learn more about Flexible Orchestration modes, visit https://aka.ms/orchestrationModeVMSS.
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0
- Consider using the image alias including the version of the distribution you want to use in the "-ImageName" parameter of the "New-AzVmss" cmdlet. On April 30, 2023, the image deployed using `UbuntuLTS` will reach its end of life. In November 2023, the aliases `UbuntuLTS`, `CentOS`, `Debian`, and `RHEL` will be removed.
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0

## Az.DesktopVirtualization

Expand All @@ -52,45 +60,115 @@ title: Upcoming breaking changes in Azure PowerShell

- Cmdlet breaking-change will happen to all parameter set
- The cmdlet is being deprecated. There will be no replacement for it.
- This change is expected to take effect from version: 2.0.0 and Az version: 11.0.0

### `Get-AzPowerBIWorkspaceCollection`

- Cmdlet breaking-change will happen to all parameter set
- The cmdlet is being deprecated. There will be no replacement for it.
- This change is expected to take effect from version: 2.0.0 and Az version: 11.0.0

### `Get-AzPowerBIWorkspaceCollectionAccessKey`

- Cmdlet breaking-change will happen to all parameter set
- The cmdlet is being deprecated. There will be no replacement for it.
- This change is expected to take effect from version: 2.0.0 and Az version: 11.0.0

### `New-AzPowerBIWorkspaceCollection`

- Cmdlet breaking-change will happen to all parameter set
- The cmdlet is being deprecated. There will be no replacement for it.
- This change is expected to take effect from version: 2.0.0 and Az version: 11.0.0

### `Remove-AzPowerBIWorkspaceCollection`

- Cmdlet breaking-change will happen to all parameter set
- The cmdlet is being deprecated. There will be no replacement for it.
- This change is expected to take effect from version: 2.0.0 and Az version: 11.0.0

### `Reset-AzPowerBIWorkspaceCollectionAccessKey`

- Cmdlet breaking-change will happen to all parameter set
- The cmdlet is being deprecated. There will be no replacement for it.
- This change is expected to take effect from version: 2.0.0 and Az version: 11.0.0

## Az.RecoveryServices

### `Get-AzRecoveryServicesVaultSettingsFile`

- Parameter breaking-change will happen to all parameter sets
- `-Certificate`
- Parameter is being deprecated without being replaced
- This change is expected to take effect from version: 7.0.0 and Az version: 11.0.0

## Az.Storage

### `New-AzDataLakeGen2SasToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageAccount`

- Cmdlet breaking-change will happen to all parameter set
- Default value of AllowBlobPublicAccess will be changed from True to False in a future release. When AllowBlobPublicAccess is False on a storage account, it is not permitted to configure container ACLs to allow anonymous access to blobs within the storage account.
- Default value of AllowBlobPublicAccess and AllowCrossTenantReplication will be changed from True to False in a future release.
When AllowBlobPublicAccess is False on a storage account, it is not permitted to configure container ACLs to allow anonymous access to blobs within the storage account.
When AllowCrossTenantReplication is False on a storage account, cross AAD tenant object replication is not allowed.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageAccountSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageBlobSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageContainerSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageContext`

- Parameter breaking-change will happen to all parameter sets
- `-EnableLargeFileShare`
- EnableLargeFileShare parameter will be deprecated in a future release.
- `-SasToken`
- The SAS token in created Storage context properties 'ConnectionString' and 'StorageAccount.Credentials' won't have the leading question mark '?' in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageFileSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageQueueSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageShareSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `New-AzStorageTableSASToken`

- Cmdlet breaking-change will happen to all parameter set
- The leading question mark '?' of the created SAS token will be removed in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

### `Set-AzStorageAccount`

- Parameter breaking-change will happen to all parameter sets
- `-EnableLargeFileShare`
- EnableLargeFileShare parameter will be deprecated in a future release.
- This change is expected to take effect from version: 6.0.0 and Az version: 11.0.0

0 comments on commit 04bc8f8

Please sign in to comment.