OpenText TeamSite Authoring Services - Microsoft Planner Integration and Automation

Common Integration Use Cases Between OpenText TeamSite Authoring Services and Microsoft Planner

1. Content publishing task creation from TeamSite workflows

When a page, campaign asset, or content package enters an approval stage in OpenText TeamSite Authoring Services, an associated task can be created automatically in Microsoft Planner for reviewers, editors, legal, or brand stakeholders. This keeps publishing work visible to cross-functional teams that may not work directly in TeamSite.

• Direction: OpenText TeamSite Authoring Services to Microsoft Planner
• Business value: Faster approvals, fewer missed handoffs, clearer accountability
• Example: A new homepage update triggers Planner tasks for SEO review, legal approval, and final sign-off

2. Planner-based campaign coordination linked to TeamSite content delivery

Marketing teams can use Microsoft Planner to manage campaign timelines, while TeamSite holds the actual content being produced and approved. Integration can sync key milestones such as draft complete, review complete, and publish date so campaign managers can track content readiness without leaving Planner.

• Direction: Bi-directional
• Business value: Better campaign visibility and tighter alignment between planning and execution
• Example: A product launch plan in Planner reflects the status of landing page and banner content managed in TeamSite

3. Automated task assignment for content review and remediation

If content in TeamSite fails a workflow rule, misses metadata requirements, or requires remediation, a Planner task can be assigned to the responsible content owner. This helps operational teams resolve issues quickly and ensures content quality standards are met before publication.

• Direction: OpenText TeamSite Authoring Services to Microsoft Planner
• Business value: Improved content governance and reduced publishing delays
• Example: Missing accessibility text on an image creates a Planner task for the content editor

4. Publishing readiness tracking for distributed teams

Organizations with distributed marketing, legal, and regional teams can use Planner as a shared readiness board while TeamSite manages the content lifecycle. Integration can update Planner task status when content is approved, localized, or scheduled for release in TeamSite.

• Direction: OpenText TeamSite Authoring Services to Microsoft Planner
• Business value: Better coordination across regions and functions
• Example: A regional campaign board in Planner shows when translated content is ready for each market

5. Content request intake from business teams into TeamSite work queues

Business users can submit content requests through Microsoft Planner, and those requests can be converted into structured work items in TeamSite for authors and editors. This creates a simple intake process for teams that do not use the content management platform directly.

• Direction: Microsoft Planner to OpenText TeamSite Authoring Services
• Business value: Streamlined request handling and reduced email-based coordination
• Example: A sales team requests a new product page update in Planner, which becomes a TeamSite authoring task

6. Status synchronization for executive and stakeholder reporting

TeamSite workflow states can be mapped to Planner task progress so stakeholders can monitor content delivery at a glance. This is useful for leadership teams that need visibility into publishing progress without accessing the CMS.

• Direction: OpenText TeamSite Authoring Services to Microsoft Planner
• Business value: Improved transparency and easier status reporting
• Example: Planner shows whether a campaign asset is in draft, under review, approved, or published

7. Cross-team issue management for content defects and post-publish updates

If a published page requires correction, TeamSite can trigger a Planner task for the appropriate team, such as content, design, or compliance. Planner then serves as the coordination layer for remediation while TeamSite manages the content update and republish process.

• Direction: OpenText TeamSite Authoring Services to Microsoft Planner
• Business value: Faster issue resolution and clearer ownership of post-launch fixes
• Example: A broken link on a published page generates a Planner task for the web content team

8. Bi-directional collaboration for content operations and campaign execution

For mature digital teams, TeamSite and Planner can work together as a connected operating model. TeamSite manages structured content workflows, while Planner manages team execution, dependencies, and deadlines. Updates in either system can keep both content creators and business stakeholders aligned.

• Direction: Bi-directional
• Business value: Stronger operational control and improved collaboration across content and marketing teams
• Example: A content approval in TeamSite updates the related Planner task, and a deadline change in Planner alerts the content owner in TeamSite