Provide a Native Anaplan Connector for Microsoft Power Automate

ToshiYAMAMOTO

In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:

Anaplan currently does not provide a native connector for Microsoft Power Automate.In our enterprise environment, this is a critical limitation because the Power Automate HTTP connector is not allowed due to internal security and compliance policies. Direct HTTP calls to external services are restricted, as endpoint security and trust cannot be sufficiently guaranteed.As a result, common workarounds—such as calling Anaplan REST APIs via the HTTP connector—are not permitted at all.While custom connectors may be considered, they still require complex API definitions, authentication handling, certificate management, and strict security reviews, making them difficult to govern and maintain.Because of these constraints, there is currently no compliant way to integrate Anaplan with Power Automate, even though Power Automate is the standard, approved automation platform for Microsoft 365 in our organization.This prevents us from implementing valuable automation scenarios, including:

• Triggering Anaplan imports from SharePoint file uploads
• Exporting Anaplan data and distributing it via Teams or Outlook
• Building approval workflows that combine Anaplan data with Microsoft services

How often is this impacting your users?

This impacts users frequently.Integration between Anaplan and Microsoft 365 services is required on a daily to weekly basis, and the lack of a compliant solution forces manual or fragmented processes.

Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)

• Solution architects and integration experts
• Anaplan model builders
• IT and security administrators
• Business and end users
• Partners and system integrators

What would your ideal solution be? How would it add value to your current experience?

The ideal solution would be an official, native Anaplan connector for Microsoft Power Automate, provided and supported by Anaplan.Such a connector should:

• Be certified within the Power Platform ecosystem
• Use secure, enterprise-grade authentication (e.g., OAuth / SSO)
• Eliminate the need for HTTP connectors or direct API handling
• Provide standard actions for imports, exports, and processes

This would enable secure and compliant integration, reduce operational risk, and allow Anaplan to fully participate in low-code automation scenarios.These HTTP connector restrictions are common across regulated and security-conscious industries such as manufacturing, healthcare, life sciences, and financial services.A native Power Automate connector would therefore address a broad enterprise adoption barrier, not a single-organization issue.

Please include any images to help illustrate your experience.

Joyce922Gaut

You’ve described the limitation very clearly: Anaplan lacks a native connector for Microsoft Power Automate, and because your enterprise disallows the HTTP connector for security/compliance reasons, you’re blocked from using REST API calls. Even custom connectors aren’t viable since they require complex API definitions, authentication, certificate management, and heavy governance overhead.
This means there’s currently no compliant integration path between Anaplan and Power Automate, despite Power Automate being the approved automation platform in your Microsoft 365 environment. As a result, valuable automation scenarios—like triggering Anaplan imports from SharePoint uploads, exporting data to Teams/Outlook, or building approval workflows—cannot be implemented.
Impact:

• Frequency: Daily to weekly, since integration with Microsoft 365 services is a recurring need.
• Audience: Model builders, solution architects, admins, integration experts, business users, and even executive-level users who rely on streamlined workflows.
  In short, the absence of a native connector forces manual, fragmented processes and prevents secure, compliant automation, creating a significant productivity gap across multiple user groups.
  Would you like me to help frame this into a formal feature request (with problem statement, business impact, and expected benefits) so it’s ready to submit to Anaplan’s product team or your internal IT governance board?