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
Details of the scenario you tried and the problem that is occurring
If a CAP include or exclude Guest or External Users, they are not reflected in the exported configuration.
Also is not possible to include Guest or External Users in the configuration.
These Attribute are only available in the beta profile (preview)
Verbose logs showing the problem
Suggested solution to the issue
Expand the Resource with "includeGuestsOrExternalUsers" and "excludeGuestsOrExternalUsers" and the sub attribute "guestOrExternalUserTypes" and "externalTenants" ,"membershipKind"
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.301.1
The text was updated successfully, but these errors were encountered:
sandrola
changed the title
AADConditionalAccessPolicy
AADConditionalAccessPolicy Guest or External User not processed
Mar 6, 2023
Details of the scenario you tried and the problem that is occurring
If a CAP include or exclude Guest or External Users, they are not reflected in the exported configuration.
Also is not possible to include Guest or External Users in the configuration.
These Attribute are only available in the beta profile (preview)
Verbose logs showing the problem
Suggested solution to the issue
Expand the Resource with "includeGuestsOrExternalUsers" and "excludeGuestsOrExternalUsers" and the sub attribute "guestOrExternalUserTypes" and "externalTenants" ,"membershipKind"
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.301.1
The text was updated successfully, but these errors were encountered: