back to worker quest hub

planner visibility retest

Generated: 2026-06-29 10:33 PT

result

Planner visibility is not ready for worker launch.

The website still has the preserved dispatch/mirror Planner ID directory, but the current connected Microsoft account does not see any Planner plans through either the Teams Planner connector or the Azure/Graph session.

preserved website directory

The worker hub currently publishes the earlier Planner dispatch directory:

• Plans: 21
• Buckets: 167
• Tasks: 1,700
• Duplicate bucket IDs: 0
• Evidence: outputs/planner-id-directory.html
• Data: assets/data/planner-task-directory.json

These IDs should not be deleted, replaced, or regenerated casually. They are the website-compatible dispatch layer until a new verified Planner source is intentionally approved.

connector visibility test

Tool:

```text
microsoft teams planner list plans
```

Result:

• Visible plans: 0

azure graph visibility test

Command:

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -File launch\test-planner-graph-access.ps1
```

Account returned by Graph:

• Display name: Jupiter Marie
• User principal name: hello@ravefocus.com
• User id: f3a619e8-52f4-4df0-a803-fc0d4f02ad7e

Planner result:

• @odata.count: 0
• value: empty
• Evidence: outputs/planner-graph-access.json

current decision

Keep the website mapped to the preserved Planner ID directory.

Do not replace the current 21-plan / 1,700-task directory with an empty Graph result.

Do not claim Planner Premium/Plan 3 launch completion until:

1. The correct Microsoft account can see the intended Planner plans.
2. Premium plans/portfolio/custom fields are created or verified.
3. Real plan IDs, bucket IDs, custom fields, and SharePoint/List links are captured in the setup packet.
4. The website directory is intentionally reconciled against the verified live Planner source.

unblock needed

Use one of these paths:

1. Sign into the Microsoft connector and Azure Graph session with the account that owns or can access the RaveFocus Planner plans.
2. Add hello@ravefocus.com to the Microsoft 365 group/team that owns the dispatch Planner plans.
3. Recreate the Planner dispatch system only if the preserved IDs are intentionally being replaced, then update the website and setup packet from the new verified IDs.

After unblocking, rerun:

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -File launch\test-planner-graph-access.ps1
npm.cmd run build:planner-id-directory
npm.cmd run verify
```