roos-fs tasks #557
open
Integrate Microsoft Planner View via Embedded or Linked Interface
0%
Description
We want to provide users with quick access to their Microsoft Planner board directly from within our application.
The idea is to have a new menu item in the sidebar called “MS Planner”.
When the user clicks on it, the main content area should display the Microsoft Planner overview (ideally as an embedded view or linked integration).
However, since Microsoft Planner does not support direct embedding through an <iframe> (As far as I understood) due to authentication and CSP (Content Security Policy) restrictions, we need to explore alternative approaches for integration.
Expected Result:
- A new navigation item in the sidebar labeled “MS Planner”.
- Clicking this item opens a Microsoft Planner overview in the main content area.
- investagte the option for implimentation and provide estimations and solution options.
- If iframe embedding is not possible, a seamless redirection or integrated experience via Microsoft Graph or link-out should be implemented.
Updated by Ivan Danyliv 7 months ago
1. iFrame Embedding
Not possible due to Microsoft’s Content Security Policy (CSP) — the Planner page blocks loading in external iframes (X-Frame-Options: DENY).
2. Redirect / External Link (Simple link-out)
Idea: Clicking “MS Planner” opens Microsoft Planner (https://tasks.office.com/ or a specific planId) in a new or the same tab.
Pros:
- Easiest solution, quick to implement
- No API or Azure setup required
- Uses existing Microsoft 365 SSO if the user is already logged in
Cons:
- Opens an external UI (not integrated visually)
- No control over the layout or embedded content
Conclusion:
Suitable as a temporary or fallback solution.
Estimation: ~8 hours
3. Microsoft Graph API Integration (Recommended)
Idea: Integrate with Microsoft Graph API to fetch and display Planner data directly inside application UI.
Pros:
- Fully integrated user experience
- Customizable view (filters, sorting, search)
- Secure and officially supported by Microsoft Graph
- Works with Azure AD SSO
Cons:
- Requires Azure AD App registration and admin consent
- Token refresh logic needed
- Higher implementation effort
Conclusion:
Best option for a production-grade integration.
Estimation: on average 45, it depends on whether Microsoft Developer account and Planner already availableor Need to create a Microsoft Developer account and set up Planner
Updated by Vadim Pariev 2 months ago
- Assignee changed from Ivan Danyliv to Vadim Pariev
Updated by