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.
<policies>
<inbound>
<base />
<rate-limit-by-key calls="10"
renewal-period="60"
increment-condition="@(context.Response.StatusCode == 200)"
counter-key="@(context.Request.IpAddress)"
remaining-calls-variable-name="remainingCallsPerIP"/>
</inbound>
<outbound>
<base />
</outbound>
</policies>
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.
Reference:
https://docs.microsoft.com/en-us/azure/api-management/api-management-access-restriction-policies

Explanation:

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.
Reference:
https://docs.microsoft.com/en-us/power-automate/connection-dynamics365

Scenario: A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.
DIFFINDAYS (date and time, date and time): Returns the difference in days between two Date and Time fields. If both dates and times fall on the same day, the difference is zero.
Note: Whenever we talk about history, the bone of contention are the below four fields:
CreatedOn
ModifiedOn
CreatedBy
ModifiedBy
Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/define-calculated-fields

Explanation:

Step 1: Call the login logic.
Step 2: Retrieve the Course credit entity metadata by using RetrieveEntityRequest with EntityFilters = Attributes and LogicalName The RetrieveEntityRequest.EntityFilters property gets or sets a filter to control how much data for the entity is retrieved.
Step 3: Define the AttributeMetaData for each new field.
Step 4: Call the RetrieveAttributeRequest with LogicalName for each new field.
The RetrieveAttributeRequest contains the data that is needed to retrieve attribute metadata.
Reference:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.messages.retrieveentityrequest.entityfilters?
view=dynamics-general-ce-9