Is there a way to create role-specific competency frameworks in Microsoft 365?

Yes, Entra + SharePoint + Power Automate can handle this. Entra supplies the employee attributes, while SharePoint holds the competency frameworks and assignment rules. The mapping between them is something you build; Entra does not provide a competency-framework engine itself.

A practical setup would be:

1. Store frameworks and rules in SharePoint Lists. Keep competencies, framework versions and assignment rules separately. For example: Engineering department → engineering framework; Sales department → sales framework; manager flag → additional leadership framework.
2. Give managers an explicit attribute or mapping. The manager field identifies someone’s manager; it does not indicate that the employee manages others. Use a maintained manager flag or determine this from reporting relationships.
3. Run a scheduled Power Automate flow. Read the relevant Entra attributes using the Office 365 Users connector where supported, or Microsoft Graph for broader coverage. A scheduled comparison is a straightforward starting point; do not assume every profile change has a ready-made flow trigger.
4. Apply all matching frameworks. Store assignments against the employee’s Entra object ID rather than their display name. Add missing assignments and end-date assignments that no longer apply, while keeping previous assessments and framework versions.

Entra dynamic groups can simplify department-based targeting if you already use them, but they require appropriate Entra licensing and membership changes are not immediate. They also do not replace the competency records or assessment workflow.

For a lightweight competency matrix, Lists and Power Automate are a reasonable fit. If you need proficiency scoring, evidence, approval cycles and detailed assessment history, consider Power Apps with Dataverse or a dedicated skills platform connected to Entra. Check connector and platform licensing before choosing that route.

Keep individual assessments in a properly restricted location. Filtering a SharePoint view to “my records” does not prevent users from accessing other records they have permission to read.