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: docs-conceptual/azps-14.4.0/breaking-changes-generated-modules.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,40 @@ upgrading the code generation tool for Azure PowerShell modules.
22
22
> breaking changes may occur, please refer to the
23
23
> [breaking change list](/powershell/azure/upcoming-breaking-changes) for the specific module.
24
24
25
+
## Identity Parameter Updates
26
+
27
+
Removed -IdentityType parameter and introduced clearer switches and parameters:
28
+
29
+
- -EnableSystemAssignedIdentity
30
+
31
+
Default value: false.
32
+
Must be explicitly added if a SystemAssigned Identity is required.
33
+
34
+
- -UserAssignedIdentity
35
+
36
+
Type: array of id strings
37
+
Accepts one or more User Assigned Managed Identities.
38
+
39
+
### How to mitigate the impact of breaking changes
40
+
41
+
- Replace old -IdentityType values with explicit parameters:
42
+
43
+
- SystemAssigned → -EnableSystemAssignedIdentity
44
+
- UserAssigned → -UserAssignedIdentity, specifying the desired identity IDs
45
+
- SystemAssigned,UserAssigned → use both -EnableSystemAssignedIdentity and -UserAssignedIdentity
46
+
47
+
- Replace any previously used parameters for User Assigned identities (such as -IdentityUserAssigned or other variations, regardless of type) with -UserAssignedIdentity, which accepts an array of strings.
48
+
49
+
All original functionality remains, but scripts must be updated to use the new explicit parameters. Refer to the cmdlet documentation for exact syntax and usage.
50
+
51
+
## Removal of parameter sets
52
+
53
+
Certain complex or cumbersome parameter sets have been removed from the cmdlet. All existing functionality remains available, but users must now use the supported parameter combinations as documented.
54
+
55
+
### How to mitigate the impact of breaking changes
56
+
57
+
Users should refer to the latest cmdlet documentation to ensure they are using supported parameter set combinations.
0 commit comments