> For the complete documentation index, see [llms.txt](https://msplannertojira.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://msplannertojira.gitbook.io/docs/basics/connect-microsoft-planner-premium-eap.md).
# Connect Microsoft Planner Premium
This guide walks you through connecting Microsoft Planner Premium to the app. Premium plans are fully supported — the connector reads from and writes to them. Writing to Premium plans requires the **Planner and Project Plan 3** license.
> **Before you start:** The exact Microsoft account connected to the app must have the **Planner and Project Plan 3** license. A license assigned only to another project owner, admin, or user does not cover the connected account.
### Why is Planner Premium Setup Different?
Even though Planner Premium looks similar to regular MS Planner, it's built on a different platform (Microsoft Dataverse) with its own API. This means setup requires additional configuration steps.
***
### 1. Connect Microsoft Planner First
Before setting up Planner Premium, make sure **Microsoft Planner** is already connected on the same connection setup page. This is a prerequisite.
***
### 2. Discover Your Dataverse Environment
Click **Setup Required** under the Microsoft Planner Premium section, then click **Discover Environments**. The app will automatically scan your Dataverse environments.
Alternatively, click **Enter URL manually instead** to provide the Dataverse URL yourself (advanced).
***
### 3. Select Your Environment
You'll see a dropdown with your Dataverse environments. In most setups, Planner Premium works with the default environment marked as **(default)**.
Keep the default if you're unsure, or switch to the environment that works with your Planner Premium if you know it.
***
### 4. Validate & Connect
Click **Validate & Connect**. The app will check if the selected Dataverse environment is connected to Planner Premium.
* If successful, you'll see **Read from Premium plans** with a green checkmark — the app now has access to reading your premium data. This read check does not confirm the Microsoft license or Dataverse privileges required for writes.
* If you see an error, verify that the selected Dataverse environment contains your Planner Premium plan. Try a different environment if needed.
***
### 5. Set Up Write Permissions
Premium writes require both the Microsoft license above and Dataverse write privileges for the same connected account. These are separate requirements. The steps below configure the Dataverse privileges only; assigning a security role does not assign a Microsoft license.
Your user needs two Dataverse permissions:
* `msdyn_operationset`
* `msdyn_operationsetdetail`
These allow the app to create and update tasks in Planner Premium on your behalf.
You can either:
* **Use Autoconfigure** (recommended) — see step 6 below
* **Set up manually** — follow the [manual setup guide](/docs/basics/planner-premium-manual-setup.md)
***
### 6. Autoconfigure Roles (Admin)
If you're an admin, expand the **Autoconfigure** section:
* **Create "MS Planner Jira Sync" Role** — creates a new security role with the two required permissions, plus an application user that has this role and can assign it to others
* **Assign Role to Me** — makes the app user assign the role to your account so the app can operate on your behalf
Once complete, you'll see green checkmarks for both **Read from Premium plans** and **Write to Premium plans**. These confirm the current environment, read access, and Dataverse privilege checks; they do not assign or confirm the Microsoft license.
***
### Not an Admin?
If you're not an admin, we have an experimental feature:
1. Click **Generate Admin Setup Link**
2. Send the link to your admin
When your admin clicks the link, the same setup happens under the hood — a new role is created with the two required permissions, plus an application user with this role.
After your admin completes the setup, you'll be able to click **Assign Role to Me** from the interface to get the permissions you need.
***
### Premium Plans Are Readable, but Create or Update Fails
If Premium plans load but a task create or update fails with HTTP 400 or `Forbidden`, check these requirements separately:
1. Ask your Microsoft 365 admin to verify that **Planner and Project Plan 3** is assigned to the exact Microsoft account connected to the app.
2. Ask your Power Platform admin to verify that the same account has the required Dataverse privileges in the selected environment.
A green read check, project ownership, or a Dataverse security role does not prove that the connected account has the required Microsoft license. Do not reconnect merely because of a generic HTTP 400, `Forbidden`, or a single HTTP 401 response. Reconnect through the app when it explicitly reports `invalid_grant`, a revoked or unauthorized Microsoft grant, or when you intentionally switch to a different properly licensed connected account.
Microsoft documents the user-license requirement under [Project schedule API limitations](https://learn.microsoft.com/en-us/dynamics365/project-operations/project-management/schedule-api-preview#limitations-and-known-problems).
***
✅ You're ready to sync with Planner Premium when the read check, Dataverse privilege check, and Plan 3 license prerequisite all apply to the connected Microsoft account.
