Azure integration in dynamic crm

Azure Components For Dynamics 365 CRM
•Service bus
•Logic App
•App Service
•Web job
•Azure web API
•Azure function
•Flow
•CRM Data Export service
2

Azure Service bus
• Azure Service Bus is a cloud based messaging service providing queues and
topics with publish/subscribe semantics and rich features. This fully
managed service is available in multi or single tenant configurations with
no servers to manage or licenses to buy.
• Use Service Bus to:
• Build reliable and elastic cloud apps with messaging.
• Protect your application from temporary peaks.
• Distribute messages to multiple independent backend systems.
• Decouple your application from each other.
• Ordered messaging scaled out to multiple readers.
3

Scenario :-
• Part 1: How we can create a service bus queue in Azure portal and
registration of service endpoint using plugin registration tool
• Part 2: Do some operation in D365 and the message appears in
Service Bus Queue. Also, read the message from queue.
4

Part 1: Create service bus queue in Azure
portal
• Login to azure portal using your account
• Click on Create a Resource and in the text box type service bus
5

4. Give a unique name to service bus namespace
and fill the mandatory fields. Then click Create.
7

5) Then browse to the service bus namespace and click on Queues.
8

7. Give a unique name for queue and let’s leave the rest of the fields
as it is and click Create.
10

8. Browse to the created queue.
11

9. Click on Shared Access Policies and click Add to create a new
policy that will be used to register service end point.
12

10. Give a unique name and Tick Send and Listen
13

Browse to the policy that was created and copy the primary connection
14

Now that we are done with creating service bus queue and shared
access policy, let’s go to the plugin registration tool and connect to the
instance where we need to integrate this queue.
15

After connecting to the required instance, click on Register –> Register
New Service Endpoint.
16

Paste the connection string copied from Step 17 above and click Next.
17

3. Verify the details on this screen and click Save.
18

19
4. Now register a new step. Here, we’ll configure to create a message in
service bus queue when a new account gets created. So, let’s register the
step on create of account.

• Part 2: Create account in D365 and the message appears in Service Bus
Queue and reading the message from queue
• Let’s login to the D365 instance in which we registered the service end
point.
• Let’s create an account.
20

• After account is created, let’s browse the queue that we had created
in the Azure portal. We’ll see the active message count has been
increased to 1.
21

let’s have the connection string of service bus namespace that we have created by
following below steps:
• Browse to the service bus namespace that we had created
• Click on Shared Access Policies
22

• Browse to the key RootManageSharedAccessKey
• Copy the primary connection string. We’re going to use this in
console application.
23

Once we have this handy, use the below sample code to read the message from the service bus queue.
public void GetMessage()
{
const string connectionString = “<Primary Connection String from Step 4 above>”;
const string queueName = “<Name of the service bus queue>”;
var queueClient = QueueClient.CreateFromConnectionString(connectionString, queueName);
BrokeredMessage message = queueClient.Receive();
Dictionary<string, object> keyValuePairs = message.Properties as Dictionary<string, object>;
foreach (var pair in keyValuePairs)
{
Console.WriteLine(string.Format(“Key: {0}, Value: {1}”, pair.Key, Convert.ToString(pair.Value)));
}
message.Complete();
message.Abandon();
Console.ReadLine();
}
For executing the above piece of code, we need to install the nuget package
“WindowsAzure.ServiceBus” and use the namespace “Microsoft.ServiceBus.Messaging” . 24

• Once we are ready with above, if we execute the console application we’ll get the
output in console as shown below:
•
25
Once we read the message from queue, it’s removed from the queue.

Azure Logic Apps
• Azure Logic Apps is a cloud service that helps you schedule,
automate, and orchestrate tasks, business processes,
and workflows when you need to integrate apps, data, systems, and
services across enterprises or organizations.
• Logic Apps simplifies how you design and build scalable solutions for
app integration, data integration, system integration, enterprise
application integration (EAI), and business-to-business (B2B)
communication, whether in the cloud, on premises, or both.

How does Logic Apps work?
• Every logic app workflow starts with a trigger, which fires
when a specific event happens, or when new available
data meets specific criteria.
• These actions can also include data conversions and
workflow controls, such as conditional statements, switch
statements, loops, and branching.

Example:- this logic app starts with a Dynamics 365 trigger with the built-in
criteria "When a record is updated". If the trigger detects an event that matches this
criteria, the trigger fires and runs the workflow's actions. Here, these actions include
XML transformation, data updates, decision branching, and email notifications.

Manage Dynamics 365 records with Azure Logic
Apps
• Add Dynamics 365 trigger
• Add Dynamics 365 action
• Add filter or query
• Find record ID
• Troubleshoot failed runs
• Connector reference

Add Dynamics 365 trigger
First, add a Dynamics 365 trigger that fires when a new lead record
appears in Dynamics 365.
• In the Azure portal, open your blank logic app in Logic App Designer, if not open
already.
• In the search box, enter "Dynamics 365" as your filter. For this example, under the
triggers list, select this trigger: When a record is created

• If you're prompted to sign in to Dynamics 365, sign in now.
• Provide these trigger details:
Property Required Description
Organization
Name
Yes The name for your organization's Dynamics 365
instance to monitor, for example, "Contoso"
Entity Name Yes The name for the entity to monitor, for example,
"Leads"
Frequency Yes The unit of time to use with intervals when
checking for updates related to the trigger
Interval Yes The number of seconds, minutes, hours, days,
weeks, or months that pass before the next check

Add Dynamics 365 action
• Under your trigger, choose New step.
• In the search box, enter "Dynamics 365" as your filter. From the actions list, select
this action: Create a new record

• Provide these action details:
Property Required Description
Organization
Name
Yes The Dynamics 365 instance where you want to create the
record, which doesn't have to be the same instance in your
trigger, but is "Contoso" in this example
Entity Name Yes The entity where you want to create the record, for
example, "Tasks"

• When the Subject box appears in your action, click inside the Subjectbox so the
dynamic content list appears. From this list, select the field values to include in the
task record associated with the new lead record:
Field Description
Last name The last name from the lead as the primary contact in the record
Topic The descriptive name for the lead in the record

• On the designer toolbar, choose Save for your logic app.
• To manually start the logic app, on the designer toolbar, choose Run.
 Now create a lead record in Dynamics 365 so you can trigger your logic app's
workflow.

Add filter or query
• To specify how to filter data in a Dynamics 365 action, choose Show advanced
options in that action. You can then add a filter or order by query. For example,
you can use a filter query to get only the active accounts and order those records
by account name. For this task, follow these steps:
• Under Filter query, enter this OData filter query:statuscode eq 1
• Under Order By, when the dynamic content list appears, select Account Name.

• Azure App Service is an HTTP-based service for hosting web applications,
REST APIs, and mobile back ends. You can develop in your favourite
language, be it .NET, .NET Core, Java, Ruby, Node.js, PHP, or Python.
Applications run and scale with ease on both Windows and Linux-based
environments.
• App Service not only adds the power of Microsoft Azure to your application,
such as security, load balancing, autoscaling, and automated management.
You can also take advantage of its DevOps capabilities, such as continuous
deployment from Azure DevOps, GitHub, Docker Hub, and other sources,
package management, staging environments, custom domain, and SSL
certificates.
• With App Service, you pay for the Azure compute resources you use. The
compute resources you use is determined by the App Service plan that you
run your apps on.

Here are some key features of App Service:
• Multiple languages and frameworks - App Service has first-class support for ASP.NET,
ASP.NET Core, Java, Ruby, Node.js, PHP, or Python. You can also run PowerShell and other
scripts or executables as background services.
• DevOps optimization - Set up continuous integration and deploymentwith Azure DevOps,
GitHub, BitBucket, Docker Hub, or Azure Container Registry. Promote updates through test
and staging environments. Manage your apps in App Service by using Azure PowerShell or
the cross-platform command-line interface (CLI).
• Global scale with high availability - Scale up or out manually or automatically. Host your
apps anywhere in Microsoft's global datacenter infrastructure, and the App
Service SLA promises high availability.
• Connections to SaaS platforms and on-premises data - Choose from more than
50 connectors for enterprise systems (such as SAP), SaaS services (such as Salesforce), and
internet services (such as Facebook). Access on-premises data using Hybrid
Connections and Azure Virtual Networks.

• Security and compliance - App Service is ISO, SOC, and PCI compliant. Authenticate
users with Azure Active Directory or with social login (Google, Facebook, Twitter,
and Microsoft). Create IP address restrictionsand manage service identities.
• Application templates - Choose from an extensive list of application templates in
the Azure Marketplace, such as WordPress, Joomla, and Drupal.
• Visual Studio integration - Dedicated tools in Visual Studio streamline the work of
creating, deploying, and debugging.
• API and mobile features - App Service provides turn-key CORS support for RESTful
API scenarios, and simplifies mobile app scenarios by enabling authentication, offline
data sync, push notifications, and more.
• Serverless code - Run a code snippet or script on-demand without having to explicitly
provision or manage infrastructure, and pay only for the compute time your code
actually uses (see Azure Functions).

WebJobs
• WebJobs is a feature of Azure App Service that enables you to run a
program or script in the same context as a web app, API app, or
mobile app. There is no additional cost to use WebJobs.

• WebJob types
• The following table describes the differences
between continuous and triggered WebJobs.
Continuous Triggered
Starts immediately when the WebJob is
created. To keep the job from ending,
the program or script typically does its
work inside an endless loop. If the job
does end, you can restart it.
Starts only when triggered manually or
on a schedule.
Runs on all instances that the web app
runs on. You can optionally restrict the
WebJob to a single instance.
Runs on a single instance that Azure
selects for load balancing.
Supports remote debugging. Doesn't support remote debugging.

Create a continuous WebJob
• In the Azure portal, go to the App Service page of your App Service web app, API
app, or mobile app.
• Select WebJobs.

• In the WebJobs page, select Add.

• Use the Add WebJob settings as specified in the table.
Setting Sample value Description
Name myContinuous
WebJob
A name that is unique within an App Service app. Must start
with a letter or a number and cannot contain special
characters other than "-" and "_".
File
Upload
ConsoleApp.zip A .zip file that contains your executable or script file as well
as any supporting files needed to run the program or script.
The supported executable or script file types are listed in
the Supported file typessection.
Type Continuous The WebJob types are described earlier in this article.
Scale Multi instance Available only for Continuous WebJobs. Determines whether
the program or script runs on all instances or just one
instance. The option to run on multiple instances doesn't
apply to the Free or Shared pricing tiers.
Click OK.

The new WebJob appears on the WebJobs page.

To stop or restart a continuous WebJob, right-click the WebJob
in the list and click Stop or Start.

Web API
How to create and host on Azure Portal

How to create WEB API
• Step 1: Open Visual Studio and Create a new ASP.Net Web Application. Click Ok.
• Step 2: In the Next Window Select Web API template as shown below and Click
Ok.
• Step 3: Now your sample Web API have been created successfully. By Default you
can see three controllers in your project.
• In this case we have created a new Controller and name it as
“MyDynamicsController.cs"

Step 4: We have created Sample Web API which will return "success" as a string.
Now we have to publish it in Azure. Right Click on the project and Click Publish
Select Azure Web Apps and Click Next. Select the required Azure Subscription and Resource Group
and Click Publish .
Now the Web Api App have been successfully Hosted In Azure.

Step 5: Open portal.azure.com . Navigate to App Service you can see the
hosted App in the list.

• Step 6: Click and Open the App you Hosted. You can see list of Ribbon Buttons,
Scroll Down to Authentication/Authorization.
• On Right Side Turn On App Service Authentication -> Select Login with Azure
Active Directory. Refer Below Screen shots.

We have enabled Azure Authentication, Now we have to create App in
Azure Active Directory to access our Web Api.

Create two AAD Apps with Application Type as Web App/Api
• Select Azure Active Directory in Authentication Provider

In the next window select Express as shown Below

• Select Create New AD App and populate the Name in Create App TextBox and
Click Ok and Save.
• Now we have successfully created App to access Custom Web Api (Assume it as
Parent App).
• Navigate to Azure Active Directory -> Click App Registration.
• In the List you can see the App which we created before.

• Open the App and Copy the Client Id, which is required while consuming our web
api.
• Application Id is the Client Id here.
•Navigate to (Settings-> Owners) Check whether you are the owner of the App.
•Navigate to (Settings-> Required Permission) By default you will have Delegate
permission for Window Azure Active Directory API .

Next we have to create a new App in AAD for accessing the App which
we created before. (Assume this is Client Side App i.e used to access our
Parent AAD App)

Select Application Type as Web app/API as shown below and click on Create.

• Now we have created two Apps in AAD. (Assume First one as Parent
and Second one as Client)
• Open the client App. Navigate to Settings->Required Permission.Click
Add.

Select API and Search for Parent App and Select the app and click ok.
In the next window Allow Delegate Permission for the App as shown below.

• Grant Permission as show below.

• Now we have to create Client Secret Key for the Client App.
• Navigate to Keys-> Create New Secret Key as shown Below and Click
Save.
• Once saved the Secret key will be visible copy the key.

Client Id(Application Id) and Client Secret Key will be used to authenticate our Web Api in
code while consuming.

Azure Functions
• Azure Functions allows you to run small pieces of code (called "functions")
without worrying about application infrastructure.
• With Azure Functions, the cloud infrastructure provides all the up-to-date servers
you need to keep your application running at scale.
• A function is "triggered" by a specific type of event.
Supported triggers:-
• Responding to changes in data
• Responding to messages
• Running on a schedule
• As the result of an HTTP request.

Features
• Some key features of Azure Functions include:
• Serverless applications: Functions allow you to develop serverlessapplications on
Microsoft Azure.
• Choice of language: Write functions using your choice of C#, Java, JavaScript, Python,
and PowerShell.
• Pay-per-use pricing model: Pay only for the time spent running your code.
• Bring your own dependencies: Functions supports NuGet and NPM, giving you access to
your favorite libraries.
• Integrated security: Protect HTTP-triggered functions with OAuth providers such as
Azure Active Directory, Facebook, Google, Twitter, and Microsoft Account.
• Simplified integration: Easily integrate with Azure services and software-as-a-service
(SaaS) offerings.
• Flexible development: Set up continuous integration and deploy your code
through GitHub, Azure DevOps Services, and other supported development tools.
• Stateful serverless architecture: Orchestrate serverless applications with Durable
Functions.
• Open-source: The Functions runtime is open-source and available on GitHub.

Function Capabilities:-
• Functions is a great solution for processing bulk data, integrating systems, working with
the internet-of-things (IoT), and building simple APIs and micro-services.
• A series of templates is available to get you started with key scenarios including:
• HTTP: Run code based on HTTP requests
• Timer: Schedule code to run at predefined times
• Azure Cosmos DB: Process new and modified Azure Cosmos DB documents
• Blob storage: Process new and modified Azure Storage blobs
• Queue storage: Respond to Azure Storage queue messages
• Event Grid: Respond to Azure Event Grid events via subscriptions and filters
• Event Hub: Respond to high-volumes of Azure Event Hub events
• Service Bus Queue: Connect to other Azure or on-premises services by responding
Service Bus queue messages
• Service Bus Topic: Connect other Azure services or on-premises services by responding
to Service Bus topic messages

Pricing Plans:-
Azure Functions has three kinds of pricing plans. Choose the one that
best fits your needs:
• Consumption plan: Azure provides all of the necessary computational resources.
You don't have to worry about resource management, and only pay for the time
that your code runs.
• Premium plan: You specify a number of pre-warmed instances that are always
online and ready to immediately respond. When your function runs, Azure
provides any additional computational resources that are needed. You pay for the
pre-warmed instances running continuously and any additional instances you use
as Azure scales your app in and out.
• App Service plan: Run your functions just like your web apps. If you use App
Service for your other applications, your functions can run on the same plan at no
additional cost.

Create your first function in the Azure portal
• Sign in to Azure
• Create a function app
• Create an HTTP triggered function
• Test the function
• Clean up resources

Create a function app
• From the Azure portal menu or the Home page, select Create a resource.
• In the New page, select Compute > Function App.
• On the Basics page, use the function app settings as specified in the following
table.
Setting Suggested value Description
Subscription Your subscription The subscription under which this new function app is created.
Resource Group myResourceGroup Name for the new resource group in which to create your function app.
Function App
name
Globally unique
name
Name that identifies your new function app. Valid characters are a-z (case
insensitive), 0-9, and -.
Publish Code Option to publish code files or a Docker container.
Runtime stack Preferred
language
Choose a runtime that supports your favorite function programming
language. Choose .NET Core for C# and F# functions.
Version Version number Choose the version of your installed runtime.
Region Preferred region Choose a region near you or near other services your functions access.

Select Next : Hosting. On the Hosting page, enter the following settings.
Setting Suggested value Description
Storage account Globally unique
name
Create a storage account used by your function app. Storage
account names must be between 3 and 24 characters in
length and can contain numbers and lowercase letters only.
You can also use an existing account, which must meet
the storage account requirements.
Operating
system
Preferred operating
system
An operating system is pre-selected for you based on your
runtime stack selection, but you can change the setting if
necessary.
Plan Consumption
(Serverless)
Hosting plan that defines how resources are allocated to
your function app. In the default Consumption plan,
resources are added dynamically as required by your
functions. In this serverless hosting, you pay only for the
time your functions run. When you run in an App Service
plan, you must manage the scaling of your function app.

Select Next : Monitoring. On the Monitoring page, enter the following settings.
Setting Suggested
value
Description
Application
Insights
Default Creates an Application Insights resource of the same App
name in the nearest supported region. By expanding this
setting, you can change the New resource name or choose a
different Location in an Azure geography where you want to
store your data.

• Select Review + create to review the app configuration selections.
• On the Review + create page, review your settings, and then select Create to
provision and deploy the function app.
• Select the Notification icon in the upper-right corner of the portal and watch for
the Deployment succeeded message.
• Select Go to resource to view your new function app. You can also select Pin to
dashboard. Pinning makes it easier to return to this function app resource from
your dashboard.

Next Create the function in the new function app:

Create an HTTP triggered function
• Expand your new function app, select the + button next to Functions, choose In-
portal, and then select Continue.
• A function is created using a language-specific template for an HTTP triggered
function.
• Now, you can run the new function by sending an HTTP request.

Choose WebHook + API, and then select Create.

Test the function
• In your new function, select </> Get function URL at the top right.
• In the Get function URL dialog box, select default (Function key) from the drop-
down list, and then select Copy.

• Paste the function URL into your browser's address bar. Add the query string
value &name=<your_name> to the end of this URL and press Enter to run the
request.
• The following example shows the response in the browser:
• The request URL includes a key that is required, by default, to access your
function over HTTP.

• When your function runs, trace information is written to the logs. To see the
trace output from the previous execution, return to your function in the portal
and select the arrow at the bottom of the screen to expand the Logs.

Introducing Power Automate
• What is Power Automate?
• Power Automate is an online workflow service that automates actions across the
most common apps and services. For example, you can create a flow that adds a
lead to Microsoft Dynamics 365 and a record in MailChimp whenever someone
with more than 100 followers tweets about your company.

What can you do with Power Automate?
• You can use Power Automate to automate workflows between your
favorite applications and services, sync files, get notifications, collect
data, and much more.
• For example, you can automate these tasks:
• Instantly respond to high-priority notifications or emails.
• Capture, track, and follow up with new sales leads.
• Copy all email attachments to your OneDrive for Business account.
• Collect data about your business, and share that information with
your team.
• Automate approval workflows.

Usage of Power Automate
• A common use of Power Automate is to receive notifications. For example,
you can instantly receive an email or a push notification on your phone
whenever a sales lead is added to Dynamics 365 or Salesforce.
• You can also use Power Automate to copy files. For example, you can
ensure that any file that's added to Dropbox is automatically copied to
SharePoint, where your team can find it.
• You can monitor what people are saying about your business by creating a
flow that runs whenever someone sends a tweet with a certain hashtag.
The flow can add details about each tweet to a Facebook post, a SQL
Server database, a SharePoint list, or even a Microsoft Excel file that's
hosted on OneDrive for Business–-whichever service works for you.

Where can I create and administer a flow?
• You can create a flow and perform administrative tasks in a browser or, if you
download the Power Automate mobile app, on your phone.
• Here are some of the tasks you can perform with the mobile app:
• Turn flows on or off from wherever you are.
• See when a flow has failed.
• Review detailed run history reports.
• View and filter runs by notification type.

Menus in Power Automate
• When you sign in to Power Automate, you'll find these menus:
• Action items, where you can manage approvals and business process flows.
• My flows, where your flows reside.
• Create, where you start a new flow.
• Templates, where you can take a look at some of the most popular templates.
These should give you some great ideas for flows you want to try.
• Connectors, (formerly called Services), where you can connect from one service
to another.
• Data, where you can access entities, connections, custom connectors and
gateways.
• Solutions, where you can manage your solutions.
• Learn, where you can find information that will help you quickly ramp up on
Power Automate.

Types of flows
• Power Automate is one of the pillars of Power Platform. It provides a low code platform
for workflow and process automation. Here's a list of the different types of flows:
Flow type Use case Target
Automated
flows
Create a flow that performs one or more
tasks automatically after it's triggered by an
event.
Connectors for cloud or on-premises
services.
Button flows Run repetitive tasks from anyplace, at any
time, via your mobile device.
Scheduled flows Create a flow that performs one or more
tasks on a schedule.
Business process
flows
Define a set of steps for people to follow to
take them to a desired outcome.
Human processes
UI flows
(Preview)
Record and automate the playback of manual
steps on legacy software.
Desktop and Web applications that do
not have APIs available for automation.

Important concepts in Power Automate
• Every flow has two main parts: a trigger, and one or more actions.
• You can think of the trigger as the starting action for the flow. The trigger can be
something like a new email arriving in your inbox or a new item being added to a
SharePoint list.
• Actions are what you want to happen when a trigger is invoked. For example, the
new email trigger will start the action of creating a new file on OneDrive for
Business. Other examples of actions include sending an email, posting a tweet,
and starting an approval.
• These concepts will come into play later, when you build your own flows from
scratch.

CRM Data Export Service
• The Data Export Service is an add-on service made available on Microsoft
AppSource that adds the ability to replicate data from Common Data Service
database to a Azure SQL Database store in a customer-owned Azure subscription.
• The supported target destinations are Azure SQL Database and SQL Server on
Azure virtual machines.
• The Data Export Service intelligently synchronizes the entire data initially and
thereafter synchronizes on a continuous basis as changes occur (delta changes) in
the system

Prerequisites for using Data Export Service
• A customer owned Azure SQL Database subscription. This subscription must allow
the volume of data that is synchronized.
• The database user must have permissions at the database and schema level. The
database user is used in the data export connection string.
• Customer owned Key Vault subscription, which is used to securely maintain the
database connection string.
• Grant PermissionsToSecrets permission to the application with the id "b861dbcc-
a7ef-4219-a005-0e4de4ea7dcf." This can be completed by running the
AzurePowerShell command below and is used to access the Key Vault that
contains the connection string secret.
• DataAccess Service Export App should be downloaded from Appsource.
• Enable pop-ups for the domain https://discovery.crmreplication.azure.net/ in
your web browser. This is required for auto-sign in when you navigate to Settings
> Data Export.

Export Profile
• To export data from model-driven apps in Dynamics 365, the administrator
creates an Export Profile. Multiple profiles can be created and activated to
synchronize data to different destination databases simultaneously.
• Only entities that have change tracking enabled can be added to the Export
Profile.
• The Data Export Service does both metadata and data synchronization. Each
entity translates into one table, and each field translates into a column in the
destination database table. Table and column names use the schema name of the
metadata.
• Once activated, an Export Profile gathers statistics for data synchronization that
helps in operational visibility and diagnostics of the data exported.

Create an Export Profile
Prerequisites:-
• The Data Export Service solution is installed in your environment.
• Maintain the SQL Database connection string in the Key Vault and copy the Key
Vault URL to provide in the Export Profile
• The entities to be added to the Export Profile are enabled for change tracking.
• Your SQL Database service has enough storage space to store the data.
• You are a System Administrator in the environment.

Create Export Profile:-
• Go to Settings > Data Export.
• Review the notice, and click Continue or Cancel if you don't want to export data.
• Click New to create a new Export Profile.
• In the Properties step, enter the following information, and then click Next to
continue without connecting to the Key Vault. Clicking Validate uses the Key Vault
URL you provided to connect to the Key Vault.
• Name. Unique name of the profile. This field is mandatory.
• Key Vault Connection URL. Key Vault URL pointing to the connection string stored
with credentials used to connect to the destination database. This field is mandatory.
Continued:-

• Schema. Name for an alternative database schema. Only alphanumeric
characters are valid. This field is optional. By default, dbo is the schema that is
used for the destination SQL Database.
• Prefix. Prefix to be used for the table names created in the destination database.
This helps you easily identify the tables created for the Export Profile in the
destination database. When specified, make sure that the prefix is less than 15
characters. This field is optional and only alphanumeric characters are allowed.
• Retry count. The number of times a record is retried in case of a failure to insert
or update in the destination table. This field is mandatory. Acceptable values are
0-20 and the default is 12.
• Retry interval. The number of seconds to wait before a retry in case of a failure.
This field is mandatory. Acceptable values are 0-3600 and the default is 5.
• Write Delete Log. Optional setting for logging deleted records.

In the Select Entities step, select the entities that you want to export to the
destination SQL Database, and then click Next.

In the Select Relationships step, you can synchronize the M:N (many-to-
many) relationships that exist with the entities you selected in the previous step.
Click Next.

• In the Summary step, click Create and Activate to create the profile
record and connect to the Key Vault, which begins the
synchronization process. Otherwise, click Create to save the Export
Profile and activate later.

Table details for the destination Azure SQL Database
• The Data Export Service creates tables for both data and metadata. A table is created for each
entity and M:N relationship that is synchronized.
• Once an Export Profile is activated, these tables are created in the destination database. These
are system tables and will not have the SinkCreatedTime and SinkModifiedTime fields added.
Table name Created
<Prefix>_GlobalOptionsetMetadata Upon Export Profile activation.
<Prefix>_OptionsetMetadata Upon Export Profile activation.
<Prefix>_StateMetadata Upon Export Profile activation.
<Prefix>_StatusMetadata Upon Export Profile activation.
<Prefix>_TargetMetadata Upon Export Profile activation.
<Prefix>_AttributeMetadata Upon Export Profile activation.
<Prefix>_DeleteLog Upon Export Profile activation when the
delete log option is enabled.

Azure integration in dynamic crm

More Related Content

What's hot

Similar to Azure integration in dynamic crm

Recently uploaded

Azure integration in dynamic crm

Editor's Notes