@merill or @SamErde or @soulemike i use the preview and the stable version but both has this issues.

Is there any fix that was applied in another part of maester and can used for it too?
If the issue is solved maester support IPP connection in Pipelines.

Ohhhh, any chance this is caused by the same issue as #1045 that I fixed in #1082?

Your added switch may be useful, but we would still want a way to get valid responses when all tests are run. I'll review to see if the technique in #1082 can be used to fix all of these tests that you identified.

Here's what I was able to find out today:
“Get-ProtectionAlert” is only available if you are connected to the IPP.

When I give a user or service principal the “View-Only Configuration” right, I get the error

The term ‘Get-ProtectionAlert’ is not recognized as a name of a cmdlet, function, script file, or executable program.

When I give the user or App the Entra role “Security Reader” in Entra ID, the call works.

This is confusing, as shown here.

Source:

https://learn.microsoft.com/en-us/powershell/exchange/find-exchange-cmdlet-permissions?view=exchange-ps#use-powershell-to-find-the-permissions-required-to-run-a-cmdlet

The last entry is my sp "3b8c8c94-5e4c-45a7-a821-0a226d9196f3". This sp should have enough permissions without the entra role. But this is not the case.

@l-gosling what does your last message mean? This cannot be executed without a user logging in? If that is the case should we even proceed in accepting this pr?

@svrooij i am waiting for a response from fabian in maester365/maester#1173.

The "issue" is that the permissions in EXO don't cover the needed permission. The security reader role had do be assigned (or another permission i am currently not found but sadly no api permissions). We can try it with URBAC, but this is also no API Permission.

In the mentioned PR in the maester repo i suggest to have a validation of the needed permission for each test. If we have this. We can discuss if we want to auto connect to ipp when connecting to EXO because the permission checks avoid this errors.

I still want to make this work. One thing that I noticed is that your new option is called include_purview. In other Maester functions, the connection to the (formerly known as) "security and compliance center" with the ExchangeOnlineManagement module is referred to as SecurityCompliance. We should keep the nomenclature consistent for now.