-
Notifications
You must be signed in to change notification settings - Fork 82
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]: Case sensitive Analysis matching does not work #82
Comments
Hey @master-qwerty, that's rare and I can't reproduce your issue. Could you please let me know if it also happens with others services? E.g ExchangeOnline Thanks in advance, |
This is working. The only issue is with the Purview.
I've tried it on another physical Windows 11 machine, but the same results, PurView is not working. |
Hey @master-qwerty thanks for the quick reply! Could you please also let me know which privileges have the user? Thanks, |
I've just tested it in Windows 10 with PS 5.1, still the same PurView not working. Regarding the roles of the used account:
|
Thanks! Could you please add the -InformationAction flag to the command and see results for successful/error authentication attemps? $param = @{ Invoke-Monkey365 @param -Verbose -Debug -InformationAction Continue Thanks, |
here is it.
|
Hey @master-qwerty now I can reproduce your issue. Thanks! It seems that it is a typo error. You're executing Monkey365 with the PurView instead of Purview. To avoid misspelling commands, please make use of TAB-completion in PowerShell. The following command should work:
Also, I'll update the codebase to ensure that only lower-case is used to evaluate parameters. On the other hand, it seems that there are some small typo errors in the markdown docs, and it should also be updated. Could you please let me know if that works for you? |
It is working with I've used JSON format so TAB does not apply to that scenario. As you already wrote, I've copied it from docu: https://silverhack.github.io/monkey365/configuration/microsoft365-options/. Maybe an idea to make it case sensitivity independent? |
Hey @master-qwerty, I've updated the develop branch and this should be fixed now. Cheers, |
This issue has been automatically marked as stale because it has not had recent activity. We kindly ask you to check again if the issue you reported is still relevant in the current version of Monkey 365. If it is, update this issue with a comment, otherwise it will be automatically closed if no further activity occurs. Thank you for your contributions. |
This issue was closed because it has been inactive for 14 days since being marked as stale. If the issue is still relevant, feel free to re-open it or open a new one. |
What happened?
A clear and concise description of what the bug is or what is not working as expected
PurView report was not created.
How to reproduce it
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Collect information and export it as a selected format.
Screenshots or Logs
If applicable, add screenshots to help explain your problem.
Also, you can add logs (Please anonymize them first!). The following command may help to share a log
Invoke-Monkey365 -Instance...... -Verbose -Debug -InformationAction Continue -WriteLog
then attach heremonkey365_exceptions_%date%.log
Log file is empty, attached is a screen with verbose.
From where are you running Monkey365?
Please, complete the following information:
$PsVersionTable
]:also tested with PS Core on Windows
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: