-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG | Get-MgBetaRoleManagementDirectoryRoleAssignmentScheduleRequest #3062
Comments
The filter looks incorrect. Try removing the hardcoded '/' and just keep the variable part: -Filter "PrincipalId eq '$($PrincipalInstance)' and RoleDefinitionId eq '$($RoleDefinitionId)' and DirectoryScopeId eq '$($DirectoryScopeId)'" Instead of: -Filter "PrincipalId eq '$($PrincipalInstance)' and RoleDefinitionId eq '$($RoleDefinitionId)' and DirectoryScopeId eq '/$($DirectoryScopeId)'" |
Yammer Admin is not returned via the powershe cmdlet
There are 2 role schedules assigned to the security group. Yammer Admin and Attribute Definition Reader. |
Another datapoint, role eligibility assigned via api call aren't returned with
|
Describe the bug
Get-MgBetaRoleManagementDirectoryRoleAssignmentScheduleRequest does not return all schedule
Expected behavior
All Eligible assignments return
How to reproduce
Yammer Administrator
andAttribute Definition Reader
Attribute Definition Reader
Diving deeper, I performed graph calls which return the expected role schedule asignments.
SDK Version
2.24
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```Name Value
PSVersion 7.4.6
PSEdition Core
GitCommitId 7.4.6
OS Microsoft Windows 10.0.20348
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
The text was updated successfully, but these errors were encountered: