add /provision skill

[is-goutham]

Adds the /provision command that automates end-to-end Power Platform
environment provisioning with ESS base + Workday ISV extension.

What it does

• Creates or binds a PP environment (PAC CLI with capacity pre-checks)
• Installs ESS base + Workday ISV via pac application install
• Creates Workday SOAP + Dataverse connections (Connectivity API)
• Binds connection references to connections (Dataverse PATCH)
• Enables flows and outputs manual CPS wiring instructions
• Configures User Context Setup topic redirect
• Validates readiness via FlightCheck

Description

Introduces 7 new Python scripts and 6 skill docs that together automate provisioning a Power Platform environment with the ESS agent + Workday ISV. The skill follows the same AI-as-orchestrator pattern used by /connect and /onboarding , markdown step files guide the agent, Python scripts handle the API calls. Flow runtime binding requires a manual Copilot Studio step (PVA API needs legacy permissions not available to custom Entra apps).
Design is ISV-extensible for ServiceNow/SAP in future PRs.

Related issue

Refs #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing
  functionality to not work as expected)
• Documentation update
• Refactor / cleanup

Testing

End-to-end tested against Preprod ring.
Final run verified:
env creation, ESS + Workday ISV install, connection creation (Workday SOAP + Dataverse), connection ref binding, flow enablement, topic redirect patch and FlightCheck validation, all passing. Manual CPS wiring confirmed functional post-script.

Checklist

• My code follows the existing style
• I have added/updated tests where applicable
• I have updated documentation as needed

[microsoft-github-policy-service]

@is-goutham 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.

6. 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.
7. 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.
8. 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.
9. 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.
10. 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.

[nehaoss]

Solid work overall. Shell injection defenses (regex allowlists), OData injection guards, HTTPS validation on token-bearing requests, and token cache permission handling are all correctly implemented. Found two issues worth addressing.

[nehaoss]

Case-sensitive prefix matching for Workday flows

The prefix=True path uses name.startswith(p) which is case-sensitive, but the prefix=False path uses case-insensitive matching (p.lower() in name.lower()). The patterns are ('ESS HR Workday', 'ESS IT Workday', 'WorkdayRESTExecution').

If the Power Platform API ever returns a display name with different casing (e.g., 'ESS HR WORKDAY...'), the prefix match silently fails and those flows are not detected, causing flightcheck to incorrectly report 'No Workday flows found' (WD-001 -> NOT_CONFIGURED).

Suggestion: Normalize both sides: if any(name.lower().startswith(p.lower()) for p in patterns):

[nehaoss]

_get_all silently discards accumulated data on mid-pagination auth failure

The previous implementation returned the partially-accumulated items list on 401/403 during pagination. The new implementation returns {'_error': ...} instead, discarding any successfully-fetched pages.

If a token expires mid-pagination (e.g., page 1 of get_flows succeeds with 250 flows, page 2 returns 401), all data from page 1 is silently dropped. For environments with hundreds of flows, this could cause confusing false failures.

Suggestion: Return the error dict only when items is empty (first-page failure = real permission problem). When items is non-empty, either return the partial list with a warning, or include the partial data in the error dict: {'_error': 'insufficient_permissions', '_partial': items}.

[nehaoss]

Large feature PR (3448 additions, 24 files) adding a /provision skill. High-level observations:

1. Scope: This adds end-to-end environment provisioning - creating Power Platform environments, connections, flow bindings, and user-context topic wiring. That's a significant new capability. The 4-step structure (step1-step4 + tasks.md) follows the established pattern from /connect.

2. New scripts: 6 new Python scripts (create_env.py, create_connection.py, bind_connection_refs.py, wire_flow_bindings.py, update_user_context_topic.py, whoami.py, pp_helpers.py). These should have corresponding unit tests - I don't see test files in this PR.

3. pp_helpers.py (286 lines): This appears to be a shared utility module for Power Platform API operations. Good separation of concerns. Check for overlap with existing pp_admin_client.py in flightcheck - ensure no duplicate functions per the repo's code quality rules.

4. Auth changes (auth.py): The diff shows 13 additions / 12 deletions - verify the refactoring doesn't break existing scripts that import from auth.py.

5. FlightCheck integration: Changes to cli.py (75+/26-), environment.py, external_systems.py, workday.py, pp_admin_client.py, and runner.py suggest the provision skill also wires into FlightCheck. Ensure these changes don't regress existing check behavior.

6. Missing tests: A PR of this size adding new API-calling scripts should include unit tests with mocked responses. Consider adding tests before merge.