Free Access Microsoft PL-400 New Release

By using a Dynamics 365 connector, you can create flows that initiate when an event occurs in Dynamics 365, or some other service, which then performs an action in Dynamics 365, or some other service.

Scenario: The Adventure Works Cycles retail location performs bicycle inspections and performance tune-ups. Technicians use paper forms to document the bicycle inspection performed before a tune-up and any additional work performed on the bicycle.

Scenario: CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Imagine having a process where you want to give someone a couple of days to reply to an approval. If that someone doesn't respond in time, you want to assign a new approval to another person or group of people. To achieve this you can set the timeout in the action settings.

Scenario: User2 reports that Azure consumption for API calls has increased significantly to 100 calls per minute in the last month.

Example:

In the following example, the rate limit of 10 calls per 60 seconds is keyed by the caller IP address. After each

policy execution, the remaining calls allowed in the time period are stored in the variable remainingCallsPerIP.

renewal-period="60"

increment-condition="@(context.Response.StatusCode == 200)"

counter-key="@(context.Request.IpAddress)"

remaining-calls-variable-name="remainingCallsPerIP"/>

Note: The rate-limit-by-key policy prevents API usage spikes on a per key basis by limiting the call rate to a

specified number per a specified time period. The key can have an arbitrary string value and is typically

provided using a policy expression. Optional increment condition can be added to specify which requests

should be counted towards the limit. When this call rate is exceeded, the caller receives a 429 Too Many

Requests response status code.