PL 400 : use policy templates to modify connector behavior at runtime (Create custom connectors)

The policy template provides the structure design or framework for policy information and ensures consistency. It should be written clearly and concisely. Such a policy helps to enforce organizational standards and assess compliance at large.


In the Azure, Policy plays prominent roles and it helps to enforce organizational standards and to assess compliance at scale. Azure policy evaluates resources in Azure by comparing the properties of those resources to business rules. these business rules, described in JSON format, are known as policy definitions. Definitions include metadata and the policy rule. The defined rule can use functions, parameters, logical operators, conditions, and property alias.

In the Custom Connector, Policies are used to enforce throttling limits on API calls, to route calls to different endpoints, and so on. Policy templates are available only for custom connectors. To use a policy template, either create a new custom connector or edit an existing one.

Policies are used to change the behavior of actions and triggers through configuration.

In the some business scenarios, we need to change the design behavior during the run time and policies allow us to modify the behavior of a custom connector at runtime. we can use policies to perform data conversion, route requests, set parameter values and more. The perform this activities, we use the policy template. This template can be access from the definition tab and there are several Templates that are available to us including:

  • Set host URL
  • Set HTTP header
  • Set query string parameter

Set host URL:

By default, the host URL is hardcoded into the connector configuration. A policy, combined with a connection parameter, allows the host URL to be specified every time we create a connection by using the connector.

Set header:

Use to promote data from the connection parameters, query, or body of the request to the header. Commonly, this process is done to accommodate APIs that want specific information configured in the header.

Set query parameter:

Use for handling default values, if necessary, but the maker doesn't configure one.

Configuring the policy template changes the API properties of the connector. API properties are stored separately from the API definition for the connector. We can import an updated API definition through the portal without overwriting the policies that we have configured.

Conclusion:

The custom connector is the primary component of the Power Platform that provides cross platform communication and enhances the behavior of the platform. Policy template plays an important role to change the behavior during run time in the custom connector.

Comments

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more