set-app-registration-native

Wires a Power Apps Wrap mobile app to an Entra ID app registration in auth.config.json.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill set-app-registration-native
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: set-app-registration-native
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/mobile-apps/skills/set-app-registration-native
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill set-app-registration-native

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connecting a generated Power Apps Wrap mobile app to Microsoft Entra ID authentication requires an app registration client ID and tenant ID, and manually editing configuration files is error-prone. This Skill walks through the official Wrap app-registration flow and writes the resulting identifiers into auth.config.json with validation.

Core Features & Use Cases

  • Guided registration flow: Opens the Power Apps Wrap app-registration page for the resolved environment so the registration is created through the supported public flow rather than manual portal edits.
  • Environment and tenant resolution: Reads power.config.json, auth.config.json, and .resolved-environment.json to determine the correct environment ID and tenant ID before writing anything.
  • Validated config updates: Writes the client ID and tenant ID into auth.config.json using structured JSON editing, preserves the cached environment object, and validates the file parses correctly.
  • Use Case: After generating a mobile app with /create-mobile-app, run this Skill to paste the Entra ID client ID from the Wrap registration page and have auth.config.json updated and validated automatically.

Quick Start

Ask the assistant to wire the generated mobile app to its Entra ID app registration and paste the client ID when prompted.

Frequently Asked Questions about set-app-registration-native

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect a Power Apps Wrap mobile app to Entra ID?

Open the Power Apps Wrap app-registration page for your environment at make.powerapps.com, create the registration there, then paste the Application (client) ID. The Skill writes the client ID and resolved tenant ID into auth.config.json and validates the JSON.

How do I find the tenant ID for my Power Platform environment?

The Skill resolves the tenant automatically from .resolved-environment.json, then auth.config.json, then by running the environment resolver script against the environmentId in power.config.json. It stops rather than guessing if resolution fails.

Do I need to add redirect URIs or API permissions manually for Wrap?

No. The Power Apps Wrap app-registration page configures the native registration for you, and tenant-wide admin consent is not required for this flow. You only need to paste the resulting client ID.

What happens if I skip configuring the client ID?

The tenant ID is still preserved in auth.config.json, but msal.clientId stays blank and the app will fail to sign in. You can rerun the Skill later or paste a client ID into auth.config.json manually.

Why does the Skill say my app root is not valid?

It requires auth.config.json, app.config.js, and power.config.json in the current directory. If any are missing, run /create-mobile-app first or open the generated app folder before retrying.