assign-offline-profile — Claude Code skill: setup and features
assign-offline-profile binds users and teams to a Dataverse Mobile Offline Profile so mobile apps can download and sync offline records.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install mobile-app@power-platform-skillsWhat assign-offline-profile does
Creating an offline profile in Dataverse does not enable sync on end-user devices by itself. Power Apps mobile clients ignore the profile until an explicit membership record connects it to a user or team. This skill automates membership configuration using Dataverse Web API requests for usermobileofflineprofilemembership and teammobileofflineprofilemembership.
The workflow resolves the target environment via power.config.json, locates the profile ID from command arguments or offline-profile.json, reads current assignments, and presents a diff for review. Mutating POST or DELETE requests execute only after user approval at the confirmation gate.
Execution halts immediately if environmentId is missing from power.config.json. Team assignments also filter strictly on teamtype eq 0, which excludes Access Teams and Owner Teams.
What it helps with
- bind Dataverse offline sync profiles to specific user accounts
- assign Mobile Offline Profiles to functional teams
- remove stale user memberships from an offline profile
- inspect existing offline profile bindings before deployment
Example prompts for the agent
- Assign the mobile offline profile to my current account using --me
- Bind [email protected] and [email protected] to the active offline profile
- Remove team Service Technicians from the offline profile assignment
How to install assign-offline-profile
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install mobile-app@power-platform-skillsThis installs the whole mobile-app plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill assign-offline-profile -a claude-code3Manually: put the files in place
~/.claude/skills/assign-offline-profile/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/assign-offline-profile/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill assign-offline-profile -a codex2Manually: put the files in place
.agents/skills/assign-offline-profile/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill assign-offline-profile -a cursor2Manually: put the files in place
.cursor/skills/assign-offline-profile/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/mobile-apps/skills/assign-offline-profile2Manually: put the files in place
.github/skills/assign-offline-profile/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill assign-offline-profile -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/mobile-apps/skills/assign-offline-profileManually: put the files in place
.devin/skills/assign-offline-profile/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about assign-offline-profile
How to install assign-offline-profile in Claude Code?
Run the marketplace commands sequentially: /plugin marketplace add microsoft/power-platform-skills, followed by /plugin install mobile-app@power-platform-skills.
What does assign-offline-profile do?
It manages profile membership in Dataverse, connecting users or Manage Teams to an existing Mobile Offline Profile so their mobile clients receive offline sync.
How does the skill detect the target profile?
It inspects --profile-id or --profile-name arguments first, checks offline-profile.json in the working directory next, or fetches the profile list directly via Dataverse API.
Source text
SKILL.md · MIT
---
name: assign-offline-profile
description: Use when the user needs to bind users or teams to a Mobile Offline Profile so they actually receive offline sync on their devices. Without this, the profile exists in Dataverse but no one's app uses it.
user-invocable: false
allowed-tools: Read, Edit, Write, Grep, Glob, Bash, AskUserQuestion
model: sonnet
---
**Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first.
**References:**
- [offline-profile-schema.md](${PLUGIN_ROOT}/shared/references/offline-profile-schema.md) — `usermobileofflineprofilemembership` / `teammobileofflineprofilemembership` entity field map
- [dataverse-offline-api.md](${PLUGIN_ROOT}/shared/references/dataverse-offline-api.md) — Web API recipe (§12 — membership POSTs)
# Assign Offline Profile
Bind one or more users and/or teams to an existing Mobile Offline Profile. Without this step, the profile exists in Dataverse but is unbound — no one's app actually uses it for offline sync.
Per the maker portal's UX (the "Assign profile to user" dialog under env settings), this is a separate operation from profile creation. Many users hit "I created the profile but offline still doesn't work" — the missing piece is membership.
Before project reads or commands, apply
[app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
Resolve one absolute `working_dir` for a direct call or require the child
invocation's owner root. Keep every shell/file operation, referenced recipe,
and retry on that root and the selected environment/tenant; missing or
conflicting context is `NEEDS_CONTEXT`. File tools use `<working_dir>/...`.
Planning-phase calls may discover and propose the membership diff but must
return before the confirmation gate, POST/DELETE, or artifact updates.
## Workflow
1. Verify project + locate profile → 2. Pick users/teams → 3. Discover existing memberships → 4. Confirm diff (single gate) → 5. POST memberships → 6. Verify → 7. Summary
---
### Step 1 — Verify project + locate profile
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
environment_id=$(node -p "require('./power.config.json').environmentId || ''") || {
echo "BLOCKED: unreadable power.config.json" >&2; exit 1;
}
if [ -z "$environment_id" ]; then
echo "NEEDS_CONTEXT: selected app has no environmentId" >&2; exit 1;
fi
node "${PLUGIN_ROOT}/scripts/resolve-environment.js" "$environment_id" --no-cache --require-tenant
```
Capture `<envUrl>` and `<tenantId>` and require them to match any supplied owner
identity. Pass `--tenant-id "<tenantId>"` on every Dataverse request, including
profile lookup, `WhoAmI`, membership discovery, mutation, readback, and retries.
Profile ID resolution (in order):
| Source | Used when |
|---|---|
| `$ARGUMENTS` contains `--profile-id <guid>` | Explicit override |
| `$ARGUMENTS` contains `--profile-name <name>` | Resolve via `GET /mobileofflineprofiles?$filter=name eq '<name>'&$select=mobileofflineprofileid` |
| `<working_dir>/offline-profile.json` | Read top-level `profileId` field |
| Otherwise | `GET /mobileofflineprofiles` and present `AskUserQuestion` with the list (max 4 options) |
STOP if no profile can be resolved. Print: `Run /setup-offline-profile first, or pass --profile-id`.
> **`power.config.json` is intentionally NOT consulted here.** That file is owned by `pa app init`. The profile ID lives in `offline-profile.json` only.
### Step 2 — Pick users/teams
`$ARGUMENTS` parsing:
| Flag | Effect |
|---|---|
| `--user <upn>` (repeatable) | Add specific user(s) by UPN (`[email protected]`) |
| `--team <name>` (repeatable) | Add specific team(s) by name |
| `--me` | Add the current Dataverse user from `WhoAmI` / `systemusers(<UserId>)` — useful for solo dev demos |
| `--all-app-users` | Add every user with **System User** role in the current env (broad; intended for prod rollout — confirm at gate) |
| `--unassign-user <upn>` / `--unassign-team <name>` | Remove an existing membership rather than add |
If no flags passed, present `AskUserQuestion`:
> **Question**: "Who should receive this offline profile?"
>
> **Options** (max 4):
> - `Just me (the current user)` — equivalent to `--me`
> - `Pick specific users by UPN` — you reply with comma-separated emails in the next message
> - `Pick a team` — list env's teams and pick one
> - `All users with System User role` — equivalent to `--all-app-users`; broad scope, confirm at gate
For pick-users flow: after the choice, print:
> "Reply with comma-separated UPNs (e.g. `[email protected], [email protected]`)"
Then read the next user message and parse.
### Step 3 — Discover existing memberships
**Telemetry checkpoint: `discover_offline_profile_memberships`**
For idempotency:
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
# Existing user memberships for this profile
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> GET \
"usermobileofflineprofilememberships?\$filter=_mobileofflineprofileid_value eq <profileId>&\$select=usermobileofflineprofilemembershipid,_systemuserid_value&\$expand=systemuserid_systemuser(\$select=domainname)" \
--tenant-id "<tenantId>"
# Existing team memberships for this profile
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> GET \
"teammobileofflineprofilememberships?\$filter=_mobileofflineprofileid_value eq <profileId>&\$select=teammobileofflineprofilemembershipid,_teamid_value&\$expand=teamid_team(\$select=name)" \
--tenant-id "<tenantId>"
```
Build the set of `already-bound` UPNs and team names.
For each candidate user/team from Step 2, look up their `systemuserid` / `teamid` (skip if already in `already-bound`):
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> GET \
"systemusers?\$filter=domainname eq '<upn>'&\$select=systemuserid,fullname,domainname&\$top=1" \
--tenant-id "<tenantId>"
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> GET \
"teams?\$filter=name eq '<team-name>' and teamtype eq 0&\$select=teamid,name&\$top=1" --tenant-id "<tenantId>"
```
(`teamtype eq 0` excludes Access Teams and Owner Teams — only Manage Teams get profile assignments.)
Construct three lists:
- `to_add` — resolved IDs to POST
- `to_remove` — resolved IDs to DELETE (from `--unassign-*` flags)
- `not_found` — UPNs/team-names that didn't resolve (warn)
- `already_bound` — skipped no-ops
### Step 4 — Confirm diff (single gate)
**Telemetry checkpoint: `confirm_offline_profile_assignment_diff`**
`AskUserQuestion`:
> **Question header**: `Confirm membership changes`
>
> **Question body**:
>
> ```
> Profile: <name> (<profileId>)
>
> Will ADD:
> - User: [email protected] (Rahul Bansal)
> - User: charanma@... (Charan Mahankali)
> - Team: Field Service RMs (12 members)
>
> Will REMOVE:
> (none)
>
> Already bound (skipping):
> - User: admin@... (no-op)
>
> Could not resolve:
> - [email protected] — not in this env's system users
>
> Proceed?
> ```
>
> **Options**:
> - `Proceed`
> - `Cancel`
### Step 5 — POST memberships
**Telemetry checkpoint: `assign_offline_profile_memberships`**
For each in `to_add`, POST sequentially (parallel POSTs occasionally return 429):
**User membership:**
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> POST \
"usermobileofflineprofilememberships" \
--tenant-id "<tenantId>" \
--body '{
"[email protected]": "/mobileofflineprofiles(<profileId>)",
"[email protected]": "/systemusers(<systemuserid>)"
}' \
--include-headers
```
Expected 204 with `OData-EntityId` → capture membership GUID.
**Team membership:**
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> POST \
"teammobileofflineprofilememberships" \
--tenant-id "<tenantId>" \
--body '{
"[email protected]": "/mobileofflineprofiles(<profileId>)",
"[email protected]": "/teams(<teamid>)"
}' \
--include-headers
```
For each in `to_remove`, DELETE:
```bash
cd -- '<working_dir>' || { echo "BLOCKED: cannot enter working_dir" >&2; exit 1; }
node "${PLUGIN_ROOT}/scripts/dataverse-request.js" <envUrl> DELETE \
"usermobileofflineprofilememberships(<membershipid>)" --tenant-id "<tenantId>"
```
> **⚠️ Duplicate handling:** POSTing a membership that already exists returns `409 Conflict`. The `dataverse-request.js` wrapper's `looksLikeDuplicate` rescue treats this as silent success (the Step 3 dedup should catch most cases first). Re-runs are safe.
### Step 6 — Verify
**Telemetry checkpoint: `verify_offline_profile_memberships`**
Re-query memberships from Step 3 and assert the diff applied:
- Every `to_add` now appears in the GET response
- Every `to_remove` no longer appears
If the verification disagrees, return `BLOCKED: membership writes did not commit` and print the discrepancy.
### Step 7 — Summary
Print:
```
✓ Membership updates applied.
Profile : <name>
Total members: <N users + M teams>
Added : <list>
Removed : <list>
Skipped : <list> (already bound)
Users will receive the profile on their next mobile app sign-in. Existing
sessions need to sign out + sign in to trigger the profile pull.
```
Update `memory-bank.md` `## Offline profile` block:
```yaml
membership:
users: [rahul@..., charanma@...]
teams: [Field Service RMs]
lastAssignedAt: 2026-05-19T...
```
## Status code (final line)
- `DONE` — every requested add/remove applied; verify confirmed
- `DONE_WITH_CONCERNS: <list>` — some UPNs/teams could not be resolved, or `--all-app-users` matched 0 users (env may not have the role granted yet)
- `NEEDS_CONTEXT: <missing>` — couldn't determine profileId (no offline-profile.json, no --profile flags, no profiles in env)
- `BLOCKED: <reason>` — auth failure, profile not found in env, or verification disagreement
## Failure recovery
Memberships are individually committed (no transaction). If Step 5 fails mid-loop:
- Partially-added memberships remain (visible in env)
- Re-running with the same arguments is idempotent (Step 3 dedup catches what's already bound)
- Use `--unassign-*` to undo specific bindings if needed
© Microsoft · MIT · microsoft/power-platform-skills