Skip to content
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]: Purview scan error #130

Open
silverhack opened this issue Dec 27, 2024 · 0 comments
Open

[Bug]: Purview scan error #130

silverhack opened this issue Dec 27, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@silverhack
Copy link
Owner

What happened?
Monkey365 fails to scan when Purview service is selected.

How to reproduce it
Steps to reproduce the behavior:

  1. Execute the following command:
Invoke-Monkey365 -Instance Microsoft365 -Collect Purview -ExportTo CSV -Verbose -Debug -InformationAction Continue
  1. See error

Expected behavior
Execute Monkey365 against Purview instance with no exceptions

Additional context
Monkey365 relies on collector's folder name when searching for valid collectors, which can return incomplete results when the folder is renamed. Some folders were renamed to comply with new brand names (e.g. Security & Compliance folder was renamed to Purview).

Note That issue is partially fixed on dev branch, but the search logic must be updated

@silverhack silverhack added the bug Something isn't working label Dec 27, 2024
@silverhack silverhack self-assigned this Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant