Skip to content

Add customer Application Insights telemetry to mobile app skill - #476

Open
Prabhat Ojha (prabhatojha) wants to merge 5 commits into
mainfrom
users/prabhatojha/app-insight
Open

Add customer Application Insights telemetry to mobile app skill#476
Prabhat Ojha (prabhatojha) wants to merge 5 commits into
mainfrom
users/prabhatojha/app-insight

Conversation

@prabhatojha

Copy link
Copy Markdown

Summary

  • add explicit opt-in setup for customer-owned Application Insights resources during mobile app creation
  • keep Application Insights out of connector and data-model planning while preserving approved customer event requirements
  • generate customer-only telemetry through getCustomerTelemetryLogger() with privacy-safe property guidance
  • pass enabled appInsightsConfig from app.json directly to PowerAppsProvider so telemetry works in the fixed Dev Player

Validation

  • validated the changed mobile template layout with validate-mobile-files.js
  • confirmed the PA Wrap and skills template layouts use identical Application Insights wiring
  • verified end-to-end ingestion with PowerAppsNative.ApplicationStarted in a generated Dev Player app

Prabhat Ojha added 5 commits August 13, 2026 16:06
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: e2aed632-0a43-491c-a5f4-53f305d12657
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: e2aed632-0a43-491c-a5f4-53f305d12657
Copilot AI lite review requested due to automatic review settings August 27, 2026 09:48
@prabhatojha
Prabhat Ojha (prabhatojha) requested a review from a team as a code owner August 27, 2026 09:48
@microsoft-github-policy-service

Copy link
Copy Markdown

Prabhat Ojha (@prabhatojha) 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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds customer-owned Application Insights telemetry support to the mobile-apps plugin by wiring app.json’s expo.extra.appInsightsConfig into the runtime (PowerAppsProvider) and updating the /create-mobile-app workflow and planner/builder agent guidance so telemetry stays out of connector/data-model planning while still enabling explicit, opt-in customer event emission.

Changes:

  • Pass expo.extra.appInsightsConfig from app.json into PowerAppsProvider only when enabled is true (to support the fixed Dev Player).
  • Add an explicit opt-in Step 6.8 to /create-mobile-app to discover/select (or paste) a customer-owned Application Insights connection string and persist safe telemetry guidance.
  • Update shared instructions + planner/builder agent docs to treat Application Insights as host/runtime configuration, not a connector or data-model constraint, and to constrain customer telemetry to approved scalar properties.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
plugins/mobile-apps/template/app/_layout.tsx Imports app.json and conditionally passes appInsightsConfig into PowerAppsProvider.
plugins/mobile-apps/skills/create-mobile-app/SKILL.md Adds Step 6.8 flow for opt-in customer telemetry setup and updates workflow ordering/guardrails.
plugins/mobile-apps/shared/shared-instructions.md Documents the “Application Insights is not a connector” exception in the connector-first rules.
plugins/mobile-apps/shared/references/connector-planning.md Updates connector planning guidance to exclude Application Insights from connector inference and gating.
plugins/mobile-apps/agents/screen-planner.md Adds per-screen “Customer telemetry” spec shape (only when explicitly requested).
plugins/mobile-apps/agents/screen-builder.md Adds implementation rules for emitting customer-only telemetry via getCustomerTelemetryLogger().
plugins/mobile-apps/agents/native-app-planner.md Instructs planner to keep Application Insights outside plan gates and defer to Step 6.8.
plugins/mobile-apps/AGENTS.md Records template prep rule for appInsightsConfig + adds opt-in telemetry guidance to agent rules.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

- Customer telemetry: enabled
- Customer telemetry app ID: <slug>
- Customer telemetry resource ID: <selected-resource-id or admin-provided>
- Customer telemetry destination: one C1-owned workspace-based Application Insights resource
- `DONE_WITH_CONCERNS` requires at least one concern. If none, use `DONE`.
- Special early-return signals (`INDUSTRY_CONFIRM_REQUESTED:`, `DESIGN_VIBE_REQUESTED:`) pre-date this protocol and remain in effect — they are special-cased "ask the user one question and re-spawn me" handoffs, not terminal returns.
- The canonical orchestrator handler lives in [`skills/create-mobile-app/SKILL.md`](./skills/create-mobile-app/SKILL.md) Step 3.0. Future skills that spawn agents should reference it rather than duplicating the switch.
13. **Customer telemetry is Application Insights-specific and opt-in** — Each generated app targets one C1-owned, workspace-based Application Insights resource. `app.json` → `expo.extra.appInsightsConfig` defaults to disabled and stores its connection string, matching the Power Apps canvas-app model. Treat the value as sensitive project configuration: do not print it, write it to `memory-bank.md`, or include it in summaries. Keep `includeUserId` false unless explicitly approved.

**Key rule:** Dataverse is NOT a connector. If requirements mention custom business data / tables, that belongs in `## Data Model`, not `## Connectors`.

Application Insights telemetry is also NOT a connector. Exclude it from Gate 3 and allow planning to proceed with the actual business connectors. The orchestrator asks for the C1-owned Application Insights resource later at Step 6.8.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merge these changes to internal copy of template before merging here

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.

3 participants