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
I have the problem, that the Check Compliance pipeline is reporting issues over teams webhooks, which are not there.
For example:
I set following Sharepoint setting:
When the Check Compliance pipeline is triggered, i get the teams report, that my tenant is not in desired state.
After looking in the event logs of my self hosted runner, i see the following:
Here it says, that the desired value is true, but that is not true. I did not set it for this tenant anywhere.
I also was looking in every MOF File under C:\azuredevops-agent_work for this value, but did not find anything.
When i am looking in the sharepoint admin center, the value is also set on false.
I do also have the problem, for other settings, like Azure AD for the ConditionalAccessPolicy:
Do you know, where those values are coming from?
I am waiting for your reply.
Best regards,
Erik
The text was updated successfully, but these errors were encountered:
Hello!
I have the problem, that the Check Compliance pipeline is reporting issues over teams webhooks, which are not there.
For example:
I set following Sharepoint setting:
When the Check Compliance pipeline is triggered, i get the teams report, that my tenant is not in desired state.
After looking in the event logs of my self hosted runner, i see the following:
Here it says, that the desired value is true, but that is not true. I did not set it for this tenant anywhere.
I also was looking in every MOF File under C:\azuredevops-agent_work for this value, but did not find anything.
When i am looking in the sharepoint admin center, the value is also set on false.
I do also have the problem, for other settings, like Azure AD for the ConditionalAccessPolicy:
Do you know, where those values are coming from?
I am waiting for your reply.
Best regards,
Erik
The text was updated successfully, but these errors were encountered: