Home/Copilot Licensing/Copilot Agent Sharing Governance Malaysia
Copilot Agent Sharing Governance Malaysia
Agent sharing determines who can access an agent; publishing determines how it is exposed through Teams, websites and integrations. Sharing controls differ by zone - from disabled in zone 1, to departmental groups in zone 2, to enterprise Entra groups and catalog publishing in zone 3.
- Malaysia
- Agent sharing
- Crest Business Solutions
Free Microsoft guide
Agent Governance Whitepaper (PDF)
Download the official Microsoft whitepaper on administering and governing agents in M365 - zones, Purview, Copilot Studio admin controls, lifecycle and sharing.
Agent sharing
Sharing, publishing and zone promotion
Agent sharing determines who can access an agent; publishing determines how it is exposed through Teams, websites and integrations. Sharing controls differ by zone - from disabled in zone 1, to departmental groups in zone 2, to enterprise Entra groups and catalog publishing in zone 3.
- Sharing vs publishing distinction by zone
- Zone 1: disabled, group or viewer-only
- Zone 2: departmental Entra groups and co-authoring
- Zone 3: enterprise groups and catalog publishing
- CoE evaluation for org-wide sharing requests
- Owner reassignment and tenant-level blocking
From the governance whitepaper
Agent sharing and publishing controls
Sharing vs publishing
Sharing grants permission to access an agent within an environment. Publishing surfaces the agent through channels such as Teams, departmental sites or plugins to M365 experiences. External channels like WhatsApp and public webchat relate to publishing and are normally blocked in personal environments through organization-level publishing policies.
- Sharing: who can run or edit the agent
- Publishing: Teams, webchat and plugin exposure
- Zone 1: external publishing blocked by default
- Zone 2: internal channels only, never external
Zone-specific sharing controls
Zone 1 sharing is disabled, limited to security groups or viewer-only for peer review. Zone 2 enables departmental sharing with specific Entra groups, named users or viewer-only run access, with editor access when collaborative development is intentional. Zone 3 supports large-scale groups such as All Employees with viewer/run-only in production and formal change-controlled publishing.
- Promote zone 1 to zone 2 when team access needed
- Promote zone 2 to zone 3 when business-critical
- Environment group rules enforce connector policies on share
- Pipelines and ALM for consistent promotion between zones
CoE governance and owner management
The whitepaper v3.2 adds sharing controls and agent owner reassignment guidance. Organizations should invite employees to share agents for CoE evaluation - deciding whether agents stay in a group or become tenant-wide. IT can block non-compliant agents from MAC. Admins regularly update permissions, remove unnecessary access and reassign owners when makers change roles to maintain accountability.
- CoE evaluates shared agents against standards
- IT blocks or unblocks agents at tenant level from MAC
- Periodic permission reviews reduce vulnerabilities
- Owner reassignment ensures continued accountability
Related pages
More Copilot governance pages
FAQ
Copilot Agent Sharing Governance Malaysia - common questions
What is the difference between sharing and publishing?
Sharing controls who can access the agent. Publishing controls how the agent is exposed through Teams, websites and other channels. External webchat is publishing, not sharing.
Can agents be shared org-wide from zone 1?
No. Zone 1 is for personal productivity. Broader sharing requires promotion to zone 2 or zone 3 with appropriate connector and access controls.
How does Crest help govern agent sharing?
Yes. Crest quotes Copilot licensing and advises on PPAC sharing limits, CoE workflows, zone promotion and owner management per the Agent Governance whitepaper.
Need Copilot licensing or agent governance guidance in Malaysia?
Tell Crest Business Solutions your Copilot seat count, Studio capacity and governance goals - we will recommend the right licensing and zone strategy.