Forum Discussion
Remove a Collaborator Governance Action is not working
- May 15, 2020
Thank you for all the testing!
Raised this to MS Support and according to them it only works if the user has been added as a Direct Access not a shared link or the usual sharing that we do where we specify a specific user when sharing.
I really hope Microsoft would also support the remove collaboration when using the usual sharing.
Hi, I just tested this scenario, and it looks like the policy does not automatically remove the collaborator. In my test, I had to highlight one of the files, go to actions, and then select Remove a collaborator as shown below;
This succeeded in removing the collaborator from the file. Not a specific scenario of CAS I have tried before, but it looks to me like this may be the intended behaviour - IE, the policy matches and Investigate Files will show you the external collaborators - but then you have to explicitly remove the access.
PeterRising thank you for your response!
We are intending to do this to remove the permissions to external users. I believe that Governance Action should be a real time action once an activity has matched that policy.
https://docs.microsoft.com/en-us/cloud-app-security/governance-actions#file-governance-actions
Should this be automated?
- PeterRisingMay 12, 2020MVP
Yes I agree that it should be automated as per the guidelines in the link you provided. Thus far, I cannot get it to automate the removal of a collaborator though - the same as you are facing.
What do you see if you click the cog wheel and select Governance log?
- Mary_YvetteMay 12, 2020Brass Contributor
The Governance action for removing Collaborator is not listed there. But I can see the alert has been triggered.
- PeterRisingMay 15, 2020MVP
In my continued testing, I cannot get automated governance to take the action to remove the collaborator. However, if I change the action to Remove External users, it works, and removes all external users.
Weird that it does not do the same for collaborator though. I may open a ticket with Microsoft about this and see what response I get.