Low-Code Governance Vocabulary
5 exercises — master the governance language used in enterprise low-code programmes: Center of Excellence, shadow IT, ALM, app catalogue, and app sprawl.
0 / 5 completed
Low-code governance vocabulary quick reference
- CoE (Center of Excellence) — cross-functional team governing low-code standards, training, and risk management across the organisation
- Shadow IT — technology used without IT knowledge or approval; creates security, compliance, and operational risks
- ALM (Application Lifecycle Management) — structured management of solution lifecycle from dev → test → production
- App catalogue — central inventory of approved solutions; prevents duplication and enables reuse
- App sprawl — uncontrolled accumulation of low-code solutions without governance or lifecycle management
- DLP policy — Data Loss Prevention policy that controls which connectors can share data together
1 / 5
An enterprise decides to scale low-code adoption across 12 business units. The CTO says: "We need to establish a Center of Excellence before this gets out of hand." What is a CoE in the context of low-code, and what does it do?
The Center of Excellence is the organisational structure that makes enterprise-scale low-code adoption sustainable and governable — understanding CoE vocabulary is essential for anyone involved in low-code strategy discussions.
Core CoE responsibilities:
The Microsoft CoE Starter Kit:
Microsoft provides a free open-source CoE Starter Kit (a set of Power Apps and Power Automate flows) that a CoE team can deploy to gain visibility over the entire Power Platform tenant — apps, flows, custom connectors, environments, and license consumption — without requiring manual inventory.
Key vocabulary:
• Center of Excellence (CoE) — a cross-functional team governing low-code adoption across an organisation
• DLP policy — Data Loss Prevention policy; controls which connectors can be used together in a flow
• Environment strategy — the plan for how sandbox, development, test, and production environments are structured and access-controlled
• Tenant — in Azure/Power Platform, the entire organisation's instance; all users and environments belong to one tenant
Core CoE responsibilities:
| Responsibility | What it means in practice |
|---|---|
| Standards & templates | Approved component library, naming conventions, approved connectors list |
| Training & enablement | Citizen developer training programmes, hackathons, office hours |
| Governance enforcement | DLP policies, environment strategy, capacity management |
| Inventory & monitoring | Dashboard of all flows/apps in tenant, orphaned resource cleanup, dependency management |
| Risk management | Security review of new connectors, data classification enforcement |
The Microsoft CoE Starter Kit:
Microsoft provides a free open-source CoE Starter Kit (a set of Power Apps and Power Automate flows) that a CoE team can deploy to gain visibility over the entire Power Platform tenant — apps, flows, custom connectors, environments, and license consumption — without requiring manual inventory.
Key vocabulary:
• Center of Excellence (CoE) — a cross-functional team governing low-code adoption across an organisation
• DLP policy — Data Loss Prevention policy; controls which connectors can be used together in a flow
• Environment strategy — the plan for how sandbox, development, test, and production environments are structured and access-controlled
• Tenant — in Azure/Power Platform, the entire organisation's instance; all users and environments belong to one tenant