1. LandOffer
  2. Blog
  3. All articles
  4. Power Apps Portfolio: Share a Business App Without Assuming Recruiter Licenses

Job search

Power Apps Portfolio: Share a Business App Without Assuming Recruiter Licenses

Current Microsoft sharing and Developer Plan changes inform a portfolio handoff with an executed local workflow reference and an honest restricted-review HOLD record.

9 min readLandOffer team

A Power Apps portfolio should offer a readable review route before asking a recruiter to sign in, obtain a license or import an app. For a live canvas app, confirm the recipient's identity, appropriate use rights and underlying resource permissions separately. Copying a URL, embedding the app or exporting a package does not establish the recipient's identity, use rights or data access.

This guide reviews Microsoft's current documentation and includes an original, actually executed local Python business-workflow reference, not a Power Apps build. Its synthetic repair requests demonstrate role decisions and a completed handoff packet; no Power Apps tenant, Dataverse permission, connector, invitation or recipient session was tested. LandOffer publishes this guide; use LandOffer.ai to match the work you can demonstrate with an employer's requested skills.

Editorial illustration of a business-app developer arranging repair requests beside a readable review booklet, with access to the authoring workspace kept separate.

The current Developer Plan guide, updated October 17, 2026, includes an important environment change. Microsoft's deprecation notice says new unmanaged developer-environment creation ends November 15, 2026; suspension of existing unmanaged developer environments starts December 15, 2026; deletion starts January 15, 2027. These are announced future dates as of this article's October 23 review.

The affected scope includes environments provisioned through the free Developer Plan. Developer environments that are Managed Environments are not affected by that deprecation, but their run rights are a separate issue: the Developer Plan does not include Managed Environments use rights. Microsoft states that users need premium licensing to run apps and flows there, including makers running their own work.

Do not repeat an older “free forever” portfolio-hosting claim without that qualification. The published guidance describes preserving work through an appropriately licensed managed environment or moving solutions before suspension. We did not inspect an account's environment, convert anything or test a migration. No plan price is quoted here because no specific recipient entitlement or hosted deployment has been established.

Make the project understandable even when its hosted demonstration is unavailable. Keep an authorized, versioned explanation of the app's business task, data model, role behavior and tested outcomes. That packet preserves reviewable evidence; it does not keep a suspended app running.

Treat identity, app access and data access as separate gates

Microsoft's guest-sharing guide describes canvas-app access through Microsoft Entra B2B guest identity. Standalone canvas apps require Power Apps use rights matching their capabilities, including when embedded in SharePoint. A recruiter's ordinary browser or Microsoft 365 account is not proof that every premium app can run.

The app's resource tenant and the recipient's home tenant also matter. Record the intended identity and context rather than asking the reader to troubleshoot an unexplained login prompt. Do not call an embedded canvas app anonymous access. Microsoft's documentation distinguishes canvas-app authentication from the separate Power Pages website model; substituting a different product is not a demonstrated solution to this portfolio's licensing problem.

The canvas-sharing instructions distinguish a User who runs the app from a Co-owner who can edit and share it. Giving a reviewer authoring privileges is a different decision from offering a demonstration. Follow the least access needed for the actual review task, with permission from the environment owner.

Sharing the app also does not establish that its records are available with the correct scope. A Dataverse-backed app needs suitable table security roles. Screens that hide a field or a button do not independently prove row or field authorization. Pair the intended record-level rule with an actual platform permission test, including a rejected action and its unchanged data result.

Inventory the resources behind the visible screen

Microsoft's resource-sharing documentation lists dependencies such as data tables, connections, flows, custom connectors and gateways. Some connections can be implicitly shared; others require the recipient to establish a connection and appropriate privileges. Inspect the actual connection type instead of writing that app sharing grants everything or grants nothing.

A workflow can load its opening screen and still fail at a data read or approval action. For a genuine Power Apps project, record which role performed each operation, what data it returned and whether a dependent flow or connector completed. An author-session recording cannot prove a guest session has the same rights.

Use synthetic data for a public portfolio unless you have permission to disclose the real material. Include hidden records, exports and connection details in that review. A cropped screenshot does not protect a confidential record still present in a downloadable file. This article's local reference contains only invented studio repairs and fictional principal keys.

Worked asset one: a complete business workflow with role checks

The original Repair Queue reference models a small studio's repair approvals. It is Python code, not Power Fx, Dataverse or a Microsoft interface. Its purpose is to make the business rules inspectable before discussing what a platform implementation would need to enforce.

The synthetic records are West requests W101, W102 and W103, plus East request E201. Wren owns W101, a Draft lamp-stand repair. Cal owns submitted W102, a backdrop-rail repair. Approver Iman owns submitted W103, a tripod-latch repair. Moss owns East's submitted storage-cart repair E201.

The declared rules are specific: requesters read their own records and submit their own Draft requests; approvers read records in their tenant and decide Submitted requests, but cannot approve their own. A demonstration reviewer receives only request ID, item and state, without owner or tenant fields, and cannot make decisions. Cross-tenant access is rejected.

The actual completed path submits W101 as Wren, changing Draft to Submitted, then approves it as Iman, changing Submitted to Approved. Separate fixtures test failure and projection rules. Each starts from a fresh copy of the same synthetic store so one decision cannot silently alter a later case's starting condition.

Actual local operation Observed result Meaning within the reference
Wren reads Cal's W102 Record unavailable Other-owner read rejected
Iman approves East's E201 Record unavailable Cross-tenant decision rejected
Iman approves own W103 Decision denied Self-approval rejected
Reviewer reads W102 ID, item and state only Declared projection omits owner and tenant
Reviewer approves W102 Decision denied; store unchanged Rejected write did not mutate records
Iman approves unsubmitted W101 Submitted-state requirement error Approval requires the workflow transition

Fifteen declared cases passed in two fresh Python 3.9.6 executions. They include successful submission, approval and rejection, repeated-decision rejection, missing-record rejection and an unknown principal. Complete before/after snapshots and observed errors remain in the saved results.

A separate checker reads those JSON observations without importing the workflow implementation. It accepts the recorded selected properties, then rejects two deliberately altered in-memory controls: a denied reviewer operation that nevertheless changes a request to Approved, and a reviewer response that leaks the owner field. Both negative controls modify copies in memory; the original saved results stay unchanged.

These observations cover the authored local rules; they do not test authentication or certify data security. The caller supplies a fictional principal key, and the local source contains the synthetic records. It has no real user sign-in, server-enforced identity or Dataverse isolation. Do not put private records into this teaching artifact or present its role switch as a secure hosted app.

Worked asset two: choose and complete the reviewer handoff

Fictional candidate Jessa and reviewer Keon frame two delivery choices. Their identities and review request are illustrative; the files and model checks described here were actually created. Keon needs to understand the business process and rejected actions without setting up a development environment.

Jessa's restricted-app delivery record is complete with a HOLD decision. No Power Apps build exists for this reference. Resource tenant, guest identity, recipient entitlement, data roles, connector and flow rights, and recipient-session behavior are all unverified. No invitation, license purchase or hosted-app link is included. The HOLD record tells the reviewer why no live app link is offered and which checks remain.

Her chosen current packet is a self-contained HTML document containing the business task, completed W101 path, all 15 saved case summaries, scope statement and trace hash. Expandable sections expose the recorded observations; they do not execute a live app action. It has no external scripts, fonts, account fields or service dependency.

We inspected the packet's source and content and checked that it contained no external assets, forms or scripts. An attempted native browser opening of the local file was blocked by the browser tool's URL protocol policy. We preserved that limitation and did not test an alternate opening route. Consequently, we do not claim verified double-click rendering or a recipient-device test. The actual model execution and static packet checks are separate evidence.

The completed unsent handoff says: “Repair Queue is an independent business-workflow reference using synthetic records. The packet shows role rules, a completed submit/approve path and 15 executed Python cases. It is not a Power Apps app or a test of Microsoft permissions. No recipient account or license is needed to read this local HTML packet.”

That wording tells Keon what exists. It does not suggest the reference demonstrates canvas formulas, a connector configuration or Dataverse security. If the employer specifically requests a running Power Apps app, Jessa must describe the gap rather than relabel the Python packet as equivalent platform experience.

Editorial illustration of a reviewer comparing a readable business-process packet with a separately controlled app workspace, illustrating two distinct delivery arrangements.

An exported package is not a license-free player

Microsoft's export/import overview describes moving canvas apps between environments. It recommends solutions for application lifecycle management and gives canvas packages a narrower basic import/export scope. A package is not an executable viewer that lets an unlicensed recruiter bypass an environment.

The documented package route does not export connections, custom connectors or gateways as ready-to-use resources. Dataverse customizations require solutions instead. Importing also requires the Environment Maker role in the destination. These are meaningful setup responsibilities for a technical reviewer, not a casual instruction to “open the attachment.”

If an employer requests source or a solution package, inventory its dependencies and permitted contents, then state what opening and running it requires. Include the schema explanation and role-test record in readable form. Keep credentials, private data and unrelated instrumentation details out of an authorized handoff. No Microsoft package was exported or imported for this article.

Match the evidence to what the employer wants to inspect

Our Power BI portfolio-sharing guide addresses report views and readable backups. A business app adds actions that change records, role-specific decisions and connection-dependent behavior. A screenshot of an approved request cannot show that another role was prevented from approving it.

For an actual Power Apps portfolio, preserve the platform version context, app contribution, synthetic data, required use rights and account-specific access evidence. Keep the demonstration recording or static explanation useful on its own, while identifying which interactions it cannot reproduce. Recheck the current environment timeline before relying on a long-lived hosted link.

Choose a role on LandOffer.ai and follow its portfolio instructions. Offer the readable packet with its build, execution and file-opening limits stated upfront. Provide a restricted live review only when the appropriate identity, licensing and resource permissions have actually been confirmed.

Sources and Further Reading