Skip to content

Add purview-developer skill#270

Open
yulcodeoy wants to merge 5 commits intomicrosoft:mainfrom
yulcodeoy:add-purview-developer-skill
Open

Add purview-developer skill#270
yulcodeoy wants to merge 5 commits intomicrosoft:mainfrom
yulcodeoy:add-purview-developer-skill

Conversation

@yulcodeoy
Copy link
Copy Markdown

Summary

Adds a new purview-developer skill that teaches AI coding agents how to correctly build on the Microsoft Purview Developer Platform.

Scenarios covered

  1. Reading and applying sensitivity labels — listing tenant labels via GET /security/dataSecurityAndGovernance/sensitivityLabels
  2. Logging contentActivity events — creating audit records via POST /users/{id}/dataSecurityAndGovernance/activities/contentActivities
  3. Reading governance state — computing protection scopes and processing content via protectionScopes/compute and processContent APIs
  4. Agent Framework integration — wiring Purview middleware into Agent Framework agents using Microsoft.Agents.AI.Purview (C#) and agent-framework-purview (Python)

Key features

  • Decision guidance table: answers "which Purview surface do I call?" — Graph APIs directly vs. Agent Framework middleware
  • Working C# and Python examples for all four canonical scenarios
  • Anti-patterns section: common mistakes agents generate (wrong endpoints, legacy APIs, double-counting, wrong auth scopes, missing caching, ignoring execution mode) with correct replacements
  • "When NOT to use" section: clarifies this is for developers, not admin/portal tasks

References

All content grounded in these authoritative sources:

Add a new skill that teaches AI coding agents how to correctly build on
the Microsoft Purview Developer Platform, covering:

- Microsoft Graph Purview data security and governance APIs
- Sensitivity labels, contentActivity, protectionScopes, processContent
- Agent Framework Purview middleware (C# and Python)
- Decision guidance: when to use Graph APIs vs Agent Framework middleware
- Anti-patterns and correct replacements
- Working C# and Python examples for all four canonical scenarios

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@yulcodeoy yulcodeoy requested a review from thegovind as a code owner April 20, 2026 16:10
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

@yulcodeoy please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Yuliya Slesareva Godoy and others added 2 commits April 20, 2026 11:16
Add Scenario 5 covering Agent 365 Observability SDK integration:
- Decision table comparing Agent Framework Purview middleware vs A365 SDK
- Package references for .NET and Python (all framework extensions)
- Blueprint and governance explanation
- Updated triggers to include A365/Agent365 keywords
- Added 5 new A365 reference URLs

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Include full 7-step Agent 365 development lifecycle (build, config,
blueprint, deploy, publish, instances, marketplace), local testing
guidance (mock tooling servers, Dev Tunnels), and AI-guided setup tip.
Add references for dev lifecycle docs and Agent365-Samples repo.

Source: https://learn.microsoft.com/en-us/microsoft-agent-365/developer/a365-dev-lifecycle

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@yulcodeoy yulcodeoy marked this pull request as draft April 20, 2026 16:34
- Rename Scenario 3 to 'Apply Data Governance and Protection to Your 3P Agent'
- Replace full Scenario 5 (A365 SDK) with brief 'Agent 365 and Purview' section
  covering only the Purview telemetry relationship
- Remove A365-specific triggers, packages, lifecycle, and detailed references
- Keep pointer to dedicated Agent 365 developer skill for full A365 guidance
- Trim A365 references to only Purview-relevant URLs

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@yulcodeoy yulcodeoy marked this pull request as ready for review April 20, 2026 20:45
Fixes identified by review:

1. Auth anti-pattern: .default scope is valid at runtime; real issue is
   missing Purview permissions in Entra app registration. Rewritten.
2. C# GraphServiceClient: add explicit scopes parameter to all instances.
3. Python SDK: replace invalid lambda config pattern with typed
   RequestConfiguration; replace raw dicts with typed request body
   objects (ComputePostRequestBody, ProcessContentPostRequestBody).
4. C# request body types: use fully-qualified generated SDK types
   (ComputePostRequestBody, ProcessContentPostRequestBody).
5. Permissions table: .User is least privileged for both delegated and
   app; .All is higher privilege. Added clarifying note.
6. Scenario 1 title: 'Reading and Applying' -> 'Reading Sensitivity
   Labels' (content only shows listing, not applying).
7. Broken link: replace ../agent-365-developer/SKILL.md with docs URL.
8. Intro: 'three surfaces' -> 'two primary surfaces + A365 telemetry'.
9. ETag caching: clarify flow (cache ETag from compute, pass as
   If-None-Match to processContent, check protectionScopeState).
10. REST vs SDK naming note added.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant