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
Looking through the source code for AADAdministrativeUnit it looks like it still uses the 'beta' cmdlets throughout (Get-MgBetaDirectoryAdministrativeUnit etc).
I believe the relevant cmdlets (especially surrounding MembershipRules and ScopedRoleMembers) which used to be 'beta only' are all available in the 1.0 module now. Wondering if it is still a good idea to be using the Beta cmdlets or not?
Microsoft 365 DSC Version
1.24.228.1
Which workloads are affected
Azure Active Directory
The DSC configuration
Any configuration using AADAdministrativeUnit
Verbose logs showing the problem
N/A
Environment Information + PowerShell Version
OsName : Microsoft Windows 11 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 22621.1.amd64fre.ni_release.220506-1250
OsLanguage : en-GB
OsMuiLanguages : {en-GB, en-US}
Key : PSVersion
Value : 5.1.22621.2506
Name : PSVersion
Key : PSEdition
Value : Desktop
Name : PSEdition
Key : PSCompatibleVersions
Value : {1.0,2.0,3.0,4.0...}
Name : PSCompatibleVersions
Key : BuildVersion
Value : 10.0.22621.2506
Name : BuildVersion
Key : CLRVersion
Value : 4.0.30319.42000
Name : CLRVersion
Key : WSManStackVersion
Value : 3.0
Name : WSManStackVersion
Key : PSRemotingProtocolVersion
Value : 2.3
Name : PSRemotingProtocolVersion
Key : SerializationVersion
Value : 1.1.0.1
Name : SerializationVersion
The text was updated successfully, but these errors were encountered:
Description of the issue
Looking through the source code for AADAdministrativeUnit it looks like it still uses the 'beta' cmdlets throughout (Get-MgBetaDirectoryAdministrativeUnit etc).
I believe the relevant cmdlets (especially surrounding MembershipRules and ScopedRoleMembers) which used to be 'beta only' are all available in the 1.0 module now. Wondering if it is still a good idea to be using the Beta cmdlets or not?
Microsoft 365 DSC Version
1.24.228.1
Which workloads are affected
Azure Active Directory
The DSC configuration
Verbose logs showing the problem
N/A
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: