How to apply COE between Academy and Microsoft ? What is the Steps ?

A formal, standardized Microsoft-run application process for an academic “Center of Excellence” (CoE) isn’t described in the provided information. However, the context does describe:

• What a CoE is and how it operates (for Power Platform, data/analytics, and BI).
• How Microsoft Learn for Educators works for academic institutions.

Based on that, an academic institution can structure its internal CoE and then align it with Microsoft programs such as Microsoft Learn for Educators and the Power Platform / Fabric adoption guidance.

Below is a step-by-step approach grounded in the available guidance.

1. Define the CoE scope and responsibilities

Use the CoE guidance to define what the academic CoE will actually do.

Key actions:

1. Define scope of responsibilities for the CoE:
   • Decide if the CoE will cover Power Platform, Azure data/analytics, AI, and BI, or start narrower (for example, Power Platform + Power BI).
   • Clarify activities: governance, training, platform operations, curriculum integration, student projects, etc.
2. Identify customers:
   • Internal: students, faculty, IT staff, research groups.
   • External: industry partners, local employers.
3. Determine COE structure:
   • Centralized team in IT or a technology department, or a federated model with departmental “satellite” CoEs (for example, Engineering, Business, Data Science), similar to how Microsoft uses satellite COEs for departments.
4. Plan for future growth:
   • Start with a centralized core team and plan to extend to departmental satellites as adoption grows.

These steps follow the “Considerations and key actions” for establishing or improving a COE, including defining scope, structure, customers, and growth plans.

2. Establish the internal CoE team and operating model

From the BI/analytics CoE and BI platform examples:

1. Form the core CoE team:
   • Technical experts in Power Platform, data/analytics, and Azure.
   • Faculty champions for curriculum and pedagogy.
   • IT staff for infrastructure and hosting.
2. Define shared capabilities (for the whole institution):
   • Core platform engineering: manage data ingestion, processing, and delivery (for example, data pipelines and semantic models for analytics courses and student projects).
   • Infrastructure and hosting: IT provisions and manages Azure services and Power Platform environments.
   • Support and operations: handle access, permissions, and keep platforms running.
   • Release management: manage changes to shared datasets, apps, and environments.
3. Define dedicated deliveries:
   • For each stakeholder group (for example, a specific department), assign a small delivery team (data engineer/analytics engineer/PM equivalent) to build and maintain solutions for that group.

This mirrors how Microsoft’s BI Platform COE is structured with shared capabilities and dedicated deliveries.

3. Align with Microsoft Power Platform CoE and Fabric guidance

For emerging technologies and low-code/data scenarios, align the academic CoE with the Power Platform and Fabric CoE guidance:

1. Use Power Platform CoE concepts:
   • A Power Platform CoE drives innovation and improvement, centralizes expertise, and provides standards, consistency, and governance.
   • Define vision, metrics, and goals for the academic CoE (for example, number of students trained, solutions built, certifications achieved).
2. Foster innovation and continuous improvement:
   • Provide sandbox environments where students and faculty can experiment with Power Apps, Power Automate, and analytics without impacting production.
   • Recognize and reward successful student and faculty projects.
   • Collect feedback via surveys and focus groups to improve labs, courses, and platform usage.
   • Stay updated on new Power Platform and Fabric features and share them via internal workshops or newsletters.
3. Consider using the Power Platform CoE Starter Kit:
   • The CoE Starter Kit is a collection of components and tools to help develop a strategy for adopting and supporting Power Platform.
   • Use its Admin, Govern, and Nurture components to:
     • Gain insights into platform adoption.
     • Establish audit and compliance processes.
     • Nurture a community of makers (students and faculty).

4. Integrate Microsoft Learn for Educators

To formalize the academic side of the CoE and connect to Microsoft programs:

1. Evaluate eligibility for Microsoft Learn for Educators (MSLE):
   • Educators/faculty at higher education institutions offering accredited degrees, diplomas, certificates, or continuing education.
   • Educators at secondary schools with a STEM-focused curriculum.
2. Choose the appropriate MSLE program option:
   • Educational Institution option:
     • For institutions with multiple faculty members interested in building students’ technical skills.
     • Requires a Program Advisor who serves as the primary administrative contact and accepts the program’s business terms.
   • Individual Educator option:
     • For a single educator acting independently of the institution.
3. Sign up for MSLE:
   • Follow the MSLE overview and FAQ guidance to apply.
   • For secondary schools, be prepared to describe the STEM-focused program and how Microsoft courses will be implemented.
4. Use MSLE benefits in the CoE:
   • Bring Microsoft Official Curriculum and instructor-led training materials aligned to Microsoft Certifications into courses.
   • Use MSLE training (online learning paths, technical training sessions, virtual educator prep sessions) to prepare faculty.
   • Align CoE goals with certification outcomes (for example, number of students achieving specific certifications).

5. Proposal structure and internal documentation

While a specific Microsoft CoE proposal template is not provided, a proposal aligned with the guidance should include:

1. Vision and objectives:
   • Why the CoE is being set up, expected outcomes, and alignment with institutional strategy.
2. Scope and responsibilities:
   • Technologies covered (Power Platform, Azure data/analytics, AI, BI).
   • Activities: governance, training, curriculum integration, student projects, research support.
3. Structure and roles:
   • COE structure (centralized/unified/federated/decentralized) as described in the Fabric adoption roadmap.
   • Roles: platform engineering, infrastructure, support/operations, release management, faculty champions, student ambassadors.
4. Customers and engagement model:
   • Internal and external customers.
   • Engagement model (push, pull, or both) as recommended in the Fabric CoE checklist.
5. Funding and sustainability:
   • Funding model for the CoE (cost center, partial chargeback, etc.).
6. Metrics and KPIs:
   • KPIs/OKRs to measure effectiveness (for example, platform usage, number of solutions, certifications, research outputs).
7. Alignment with Microsoft programs:
   • Use of Microsoft Learn for Educators.
   • Use of Power Platform CoE Starter Kit and Fabric adoption roadmap.

This proposal can be used internally and as a basis for discussions with Microsoft representatives or partners.

6. Infrastructure expectations and faculty training

From the CoE and BI platform guidance:

1. Infrastructure expectations:
   • Azure services provisioned and managed by IT (infrastructure and hosting team).
   • Power Platform environments configured with appropriate governance.
   • Data platform and BI capabilities (for example, Power BI, Fabric) set up as a shared institutional platform.
2. Faculty training and support:
   • Use MSLE training resources (online learning paths, technical training sessions, virtual educator prep sessions) to prepare faculty to deliver Microsoft curriculum.
   • Use CoE Nurture components to build a community of makers and educators.
   • Provide ongoing internal workshops and knowledge-sharing sessions.

7. Engagement with Microsoft and partners

The provided context does not describe a formal Microsoft-run MoU process or partner involvement model specifically for academic CoEs. However, the following are supported by the context:

1. Use Microsoft Learn for Educators as the primary formal programmatic connection between the institution and Microsoft for curriculum and training.
2. Use the CoE guidance (Power Platform and Fabric) to design and operate the internal CoE.
3. For additional collaboration (for example, MoU, partner-led initiatives), coordinate through existing Microsoft account teams or partners using normal institutional channels; details of those processes are not covered in the provided material.

References:

• Establish a Microsoft Power Platform Center of Excellence
• Microsoft Power Platform Center of Excellence (CoE) Starter Kit
• Microsoft Fabric adoption roadmap: Center of Excellence
• How Microsoft established a Center of Excellence
• Microsoft Learn for Educators Program FAQ