Skip to main content
Question

Using Pigment APIs with a Microsoft Service Principal

  • Nov 20, 2026 4:03 PM UTC
  • 0 replies
  • 1 view

Forum|alt.badge.img+1

Hello Pigment Community,

I'm currently working on enterprise integrations between Pigment and the Microsoft ecosystem (Microsoft Entra ID / Azure AD, Power Platform, Azure services, and custom applications).

I would like to better understand the possibilities and best practices for consuming Pigment APIs through a Service Principal and would appreciate feedback from the community.

1. Authentication with Service Principals

  • Is it possible to authenticate to Pigment APIs using a Microsoft Entra ID Service Principal?
  • If yes, what authentication flow is recommended?
  • Are there specific prerequisites or configuration steps required in Pigment?
  • Is machine-to-machine authentication officially supported?

2. Available APIs

Which Pigment APIs are available for custom developments?

For example:

  • Metadata APIs
  • Data retrieval APIs
  • Data update/write APIs
  • Scenario management APIs
  • Workflow-related APIs
  • User and security administration APIs

Is there a consolidated list of APIs that can be consumed externally?

3. Typical Integration Use Cases

I would be interested in understanding how other customers are using Pigment APIs in production environments.

Examples:

  • Data synchronization with HR systems
  • Integration with Data Warehouses and Data Lakes
  • Automation through Power Automate
  • Integration with Azure Functions or Logic Apps
  • Administrative automation
  • Master data synchronization
  • Planning and forecasting process automation

4. Implementation Examples

Do you have examples of:

  • Postman collections
  • PowerShell scripts
  • Python implementations
  • .NET implementations
  • REST API examples

Especially examples using machine-to-machine authentication without user interaction.

5. API Governance and Scalability

Are there any limitations, throttling rules, rate limits, payload size restrictions, or API governance recommendations that should be considered when designing enterprise-scale integrations?

More specifically:

  • Are there any API consumption limits per workspace or per user?
  • What are the recommended patterns for high-volume data extraction or loading?
  • Are there best practices regarding batching, scheduling, and retry mechanisms?
  • Are there any performance considerations or known limitations when integrating Pigment with enterprise platforms such as Azure, Power Platform, or ETL tools?

6. Security and Access Management

Are API permissions and scopes configurable at a granular level, or does API access inherit the permissions of the associated Pigment user or service account?

More specifically:

  • What is the recommended approach for managing technical accounts?
  • Can different APIs be restricted to specific scopes or capabilities?
  • Are there best practices for segregating duties and limiting access according to the principle of least privilege?
  • How do customers typically manage API access for production integrations, audit requirements, and security reviews?

Objective

My goal is to define a robust, scalable, and secure integration architecture around Pigment APIs while following enterprise security standards, governance requirements, and automation best practices.

Any documentation, architecture recommendations, implementation examples, code samples, or lessons learned would be greatly appreciated.

Thank you in advance for your support.