Copilot will expose the cracks that already exist in permissions management.
Perry Underdown
Innovative Technology Leader specializing in Business Process Optimization and Automation leveraging Microsoft AI solutions, Power Platform, and Microsoft Azure.
Preparing for the deployment of CoPilot involves a significant focus on permissions management within the Microsoft 365 ecosystem. The potential risks associated with inadequate access controls and permissions are highlighted, particularly in the context of CoPilot's ability to surface and disseminate data.
The proposed steps for conducting a thorough audit and cleanup of M365 Groups and permissions seem comprehensive. By inventorying groups and associated members, assessing data associated with these groups, and tracking external sharing links, organizations can gain better visibility into their permission structures and identify areas for improvement.
Additionally, involving Group and Site Owners in the validation process through automated workflows in Power Automate is a practical approach to ensure participation and accountability. Automating these workflows to run periodically enhances ongoing governance and reduces the risk of permissions becoming outdated over time.
While this effort may require significant time and resources, it's crucial for mitigating potential risks associated with CoPilot and safeguarding sensitive data within the organization. By proactively addressing permission management issues, organizations can better leverage the capabilities of CoPilot while maintaining data security and compliance.
?
1.??? Inventorying M365 Groups and Associated Members:
·?????? This involves creating a script or utilizing existing tools to compile a comprehensive list of all M365 Groups within the organization.
·?????? The script should also gather information about the members associated with each group, including their roles and permissions.
2.??? Assessing Data Associated with M365 Groups:
·?????? Similar to the first step, a script or tool should be employed to inventory all data associated with M365 Groups, such as SharePoint sites, MS Teams channels, Planner Boards, etc.
·?????? This step aims to provide a holistic view of the resources accessible to each group and identify any potential areas of concern or data that may need additional protection.
3.??? Inventorying External Sharing Links:
·?????? It's essential to identify all external sharing links that grant access to content within the organization's M365 environment.
·?????? This includes documents, folders, sites, or any other resources shared with external parties, which may pose security risks if not properly managed.
4.??? Limiting Externally Shared Content:
·?????? To mitigate risks associated with external sharing, measures should be taken to limit externally shared content from being included in CoPilot's scope.
·?????? This may involve reviewing and adjusting sharing settings for sensitive data and implementing policies or controls to restrict external access where necessary.
5.??? Identifying Group and Site Owners:
·?????? Building a comprehensive list of Group Owners and SharePoint site owners is crucial for accountability and communication throughout the audit and cleanup process.
·?????? Owners play a key role in validating group memberships and ensuring the accuracy of permissions within their respective areas of responsibility.
6.??? Creating Validation Workflows:
·?????? Utilizing Power Automate or similar workflow automation tools, organizations can streamline the validation process by automating communication with Group and Site Owners.
·?????? Workflows should include notifications to owners, provide them with necessary information for auditing memberships, and facilitate their response and validation.
7.??? Tracking Owner Responses:
·?????? Tracking responses from Group and Site Owners ensures that all stakeholders participate in the validation process and that no groups or permissions are overlooked.
·?????? This step helps maintain accountability and allows for follow-up actions if owners fail to respond within a specified timeframe.
8.??? Automating Periodic Workflows:
·?????? To ensure ongoing governance and compliance, workflows should be automated to run periodically, such as every 90 days.
·?????? Regular audits help keep permissions up-to-date and aligned with organizational policies and security requirements.
9.??? Implementing Notifications and Reporting:
·?????? Implementing notifications and reporting mechanisms provides visibility into the audit and cleanup process, enabling stakeholders to track progress and identify any outstanding issues or risks.
·?????? Reports should highlight areas of improvement and provide recommendations for enhancing permissions management practices.
By following these steps, organizations can effectively mitigate the risks associated with CoPilot and ensure that sensitive data is protected against unauthorized access or exposure. This proactive approach to permissions management not only enhances security but also enables organizations to leverage the full potential of CoPilot while maintaining compliance with regulatory requirements and industry best practices.
?