This blog will have a quick walkthrough of the Microsoft Entra ID security group and team members’ management.

Managing team from Microsoft Entra ID admin center

You can navigate to Power Platform Admin Center and under Admin centers > “Microsoft Entra ID” will be available as one of the options.

On being clicked> It will redirect you to the Microsoft Entra URL Page. From within the sitemap, you can navigate to Identity > under it expand Users entity > Select All Users and that will display all the users as shown below

Managing from Azure Portal

The other way is to log to the Azure Portal > Under All services > select “Microsoft Entra ID” as shown below:

NOTE: The Azure AD product icon is replaced with the Microsoft Entra ID product icon as highlighted above.

Now let’s create a team in CRM with the type “Microsoft Entra ID Security Group” and manage the members in it. If you don’t know how to create teams in CRM then you need to refer to our previous blog wherein we have explained how to create a team of type “AAD Security Group” which is now renamed as “Microsoft Entra ID Security Group”.

When you try to create a team from Power Platform Admin Center > Select the appropriate Environment > Settings > Teams > Click on Create team > Quick create form will open as below.

You will observe that under Team Type these new renamed options are displayed. “Microsoft Entra ID Security Group” formerly called “AAD Security Group” and “Microsoft Entra ID Office Group” formerly called “AAD Office Group”.

When you select Team Types its relevant fields will be visible, as in this scenario when Team Type is selected as “Microsoft Entra ID Security Group” the below fields become visible on the form:

• Group Name
• Membership Type

• Group Name– When you start typing the group name here, it helps you to select the group from existing groups that are created already in the Microsoft Entra admin center. For this demonstration select the “Sales Team” group as below:

Before starting to enter the text, make sure groups are pre-created in the Microsoft Entra admin center. As you can see “Sales Team” was already created as a security group in the Microsoft Entra admin center below:

• Membership Type– which is defaulted to “Members and guests”, If you want you can change it to Members, Owners, or Guests as per need.

When you open the Team in CRM, you will find the “Azure AD Object Id for a group” gets auto-populated matching with the Group Object ID created in the Microsoft Entra Admin center.

Screen clip of “Sales Team” in CRM

NOTE: it is observed that in CRM when the “Entra Security Group” type team is created its associated queue is not created, and hence “Default Queue” is not granted for this type of team which does happen when you create Owner type team.

Screen clip of “Sales Team” in Microsoft Entra admin center

From within the sitemap, you can navigate to Identity > under it expand Groups entity > Select All groups, and open the appropriate team as shown below:

After creating the team, you can add members and select corresponding security roles.

NOTE: When you add members to Team from the Microsoft Entra admin center that doesn’t reflect in the CRM team instantly until that user first time accesses the environment.

As you can see from the Microsoft Entra admin center the above group has 2 team members but not all users are synced instantly to the corresponding Team created in CRM. Hence if you go and check the team members list in the CRM team it may show you a discrepancy in count as shown below only 1 member is shown below:

The simple reason for not displaying another member (Mike in our scenario) is it displays the list of users who have accessed the environment and as Mike hasn’t accessed the environment yet, Once he accesses the environment it will get instantly added in the team, and will inherit the security roles as well in run time.

NOTE: As per Microsoft the team member list in CRM doesn’t show all the group members of the Microsoft Entra group. The group member is added to or removed from the CRM group team only when a Microsoft Entra group member accesses the environment next time. You can refer Note section of this Microsoft doc for more details.

Conclusion

From within the Microsoft Entra Admin Center you can manage Groups, Group Members, Group Licensing, and Group Security quickly and easily.

The post Microsoft Entra ID Security Groups Management first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Source

The post Microsoft Entra ID Security Groups Management appeared first on Microsoft Dynamics 365 Blog.

The post Business Events in Dynamics 365 Finance and Supply Chain – How To appeared first on Ellipse Solutions.

Source

The post Business Events in Dynamics 365 Finance and Supply Chain – How To appeared first on Microsoft Dynamics 365 Blog.

We recently had a business requirement to load data in Dynamics 365 CRM. We had a case where the user will create Account records in a CRM and at the end of the day, it should load records in the other Dynamics 365 CRM. To achieve this we have used the Azure Copy Data Activity tool, also we have configured scheduling on the “Copy Data” tool so it will Upsert records in the target system once a day.

In this blog, we have explained how we have configured the ‘Azure Copy Data Activity’ tool to Load records. So, let’s have a look at the steps we followed to achieve the same.

Step 1: Connect to the Azure https://portal.azure.com and navigate to the Data factory. If you don’t have a Data factory then create it first to use the ‘Copy Data Activity tool’.  Please refer to the below link to know how to create a Data factory:

https://docs.microsoft.com/en-us/azure/data-factory/quickstart-create-data-factory-portal#create-a-data-factory

Step 2:  We already have a Data factory i.e. “DataLoadActivity”, so we are using that but to add the Copy Data Activity tool, you need to add a pipeline.

DataloadActivity (Data factory) -> Author & Monitor -> Author -> Create new/Existing Pipeline -> Drag and Drop Copy Data.

Please refer to the below screenshots:

Navigate to Author & Monitor

Navigate to Author

Add Pipeline

Drag and Drop ‘Copy Data’ tool.

We can change its name from the ‘General tab’, we have renamed it as ‘Load Accounts’.

Step 3: In the next step, we need to add a new dataset and configure a connection with Dynamics 365 CRM. To configure the dataset, we need to click on the Dataset menu and add New Dataset as shown below:

It will open the Data Stores window. Here we need to select Dataverse (Common data service for app) and click on continue.

Once the dataset is added, we need to add link services. To add link services, click on the +New button and it will open another window where we need to set CRM connection details.

Here, we need to pass details i.e., Name, Service Url, Authentication type(AAD Service Principal), Service Principal Id(Azure Active directory App Id) and service principal key(secret key) details. And after the ‘Test connection’, click on Create.

• Name: Connection name
• Connect via integration runtime: AutoResolveintegrationruntime
• Deployment Type: It has two options i.e. Online and OnpremisewithIfd. As we are connecting to Dynamics 365 CRM online, so need to select online.
• Service uri: Dynamics 365 CRM url
• Authentication Type: It has 2 options i.e. AAD service Principal and office365. Need to select ‘AAD service Principal’ option. FYI, office365 is deprecated now.
• Service Principal credential type: Select ‘service principal key’ and then it will ask to enter Azure Active directory App Id and secret key.
• Service Principal ID: Need to pass Azure Active Directory Application(client) Id.
• Service Principal Key: Need to pass Azure Active Directory Secret key.

To establish a connection, you must have Azure Active Directory and use the App Id and secret key from the Azure Active Directory app. You can refer to the below article to know about how to configure/create Azure Active Directory app:

https://www.inogic.com/blog/create-azure-active-directory-app

Once Azure Active Directory app is configured, you need to create an Application user in CRM. To configure the Application user, we need to pass Azure Active Directory Application ID (App Id) as shown below:

After this, we need to select the table name under connection. As we want to load data for the Account table so here we select the Account table. Using the same way, we have set up a dataset/connection for both Source and Target CRMs.

Step 4: Now, we can set up the “Copy Data” tool. In the first step, we need to set up a Source detail, as shown below. Here, we have selected a table but as per the requirement, we can also select Query and pass the fetchxml query.

Step 5: Next, we need to set up Sink details. Here we have selected Target CRM and selected behavior as Upsert. Also, it has other properties i.e. to ignore null values, perform upsert based on Alternate key, etc.

Note: If you don’t want to upsert the record based on the Primary key field (i.e., accountid) then you can use the Alternate key property. You need to set an alternate key in your target CRM table field and then the alternate key will display here under the Alternate key name list.

Please refer to the below article to know how we can configure alternate key in CRM:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/define-alternate-keys-reference-records?view=op-9-1#define-alternate-keys

Step 6: Once Sink details are configured, we need to set field mapping as shown below:

Note: If you don’t see mapping fields, please click on Import Schemas.

Step 7: We can also add a trigger and configure scheduling to trigger the ‘Copy Data’ tool.

It has multiple options to set trigger i.e., minutes/hourly/day/week. As per our requirement, we have set it to Day(s), as shown in the below screenshot

Step 8: Publish all.

We can also monitor the run history. To check the run history please navigate to Monitor -> Pipeline run.

Also, we can run the pipeline by clicking on Debug without setting any Trigger, please refer to the below screenshot:

Note: I couldn’t get the option/behaviour to perform only Update operation instead of using Upsert.

Conclusion:

As illustrated above, with the help of Azure Copy Data Activity tool, we can load data in Dynamics 365 CRM.

Reference link: https://docs.microsoft.com/en-us/azure/data-factory/quickstart-create-data-factory-copy-data-tool#start-the-copy-data-tool

Source

The post Load Data in Dynamics 365 CRM using Azure Copy Data Activity tool appeared first on Microsoft Dynamics 365 Blog.

Given that the Azure function is configured for AAD authentication in the Authentication / Authorization section of the function as shown below

Now that we have provided for AAD authentication that requires a user login, it would be good if all operations are executed within the context of the same user.

Within your Azure function, you can get the details of the logged-in user using the ClaimsPrincipal

ClaimsPrincipal principal = req.HttpContext.User;

if (principal.Identity != null)

{

log.LogInformation(“Claims identity ” + principal.Identity.Name);

}

if (principal.Claims != null)

{

foreach (Claim c in principal.Claims)

{

log.LogInformation(“CLAIM TYPE: ” + c.Type + “; CLAIM VALUE: ” + c.Value + “</br>”);

}

 }

In the console, you can see all the claims returned

One of the claims returned is AADID

Read this specific claim value

Claim claim = principal.Claims.FirstOrDefault(c => c.Type.Contains(“objectidentifier”));

string aadobjid = “”;

if (claim != null)

{

aadobjid = claim.Value;

log.LogInformation(“aadobjid = ” + aadobjid);

}

Every CRM User that we create has an associated AADID stored along which is this objectid.

Set this to the cds client object we have created for impersonation

//establish connection with CDS

CdsServiceClient client = new CdsServiceClient(connectionString);

if (!string.IsNullOrEmpty(aadobjid))

{

client.CallerAADObjectId = new Guid(aadobjid);

}

Do note if you run a WhoAmI request – it still returns the id of the original credentials used for establishing the connection.

However, when you create a record, you will notice that the owner of the new record is the same user that had logged in to the connector.

Source

The post Impersonation within Azure Function or Custom Connector when using AAD authentication appeared first on Microsoft Dynamics 365 Blog.

Do remember, we have enabled AAD authentication for our Azure function.

The APP registration provided while enabling AAD authentication was set for multi-tenant authentication.

While we have an easy way to create a custom connector outside the scope of a solution, since we will also cover moving custom connectors from one environment to another, we will look at the steps to create the connector from within a solution

Navigate to https://make.powerapps.com and open your solution. Next, choose New > Other > Custom Connector.

First Step provide Connector details like name, image and short description. In the host add the host name of your Azure function i.e if your azure function url was

https://xxx.azurewebsites.net/api/GetTaxRate?code=xxxx

the host would be xxx.azurewebsites.net

Next comes security. Since we are looking for AAD authentication, we will choose OAuth 2.0 in this step.

Client ID = APP ID of the App registration created while setting the AAD security for Azure function

Client Secret = Secret key of the above app.

Leave the login url and tenant id as is.

Resource URL = Copy and paste the client id (app id of the app registration)

Ref: Why leave common in tenant id –  https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant

After you save the connector, the Redirect URL will be generated as shown above. Copy the redirect URL and we need to add this to our app registration (same one of which you have provided the client id here)

Next in the Definition tab, we will provide the details of the actions that we wish to expose through our connector

Under actions choose new action and provide the action details. The details entered here will be displayed to the user when using your connector and this action so make sure to have all the descriptive information included here.

In the request section click import from sample and provide the request details. You can copy the url from Postman where we had done the test call.

My request has 2 query parameters and in the header I need to pass the CRM connection details like URL and the Client ID, Secret for connection to the said environment.

When you click import, you will see all the query parameters and header information has been generated for you.

Click Update Connector to save all changes to the connector.

Before we test the connector we need to complete a few additional settings in Azure APP registration.

Completing the authentication settings on Azure AD APP registration

Navigate to Authentication section of the App Registration

Click Add a platform

Choose Web and paste the Redirect URI copied from the connector

Click Save to save this redirect uri.

Next navigate to the Expose an API setting of the APP registration and click add scope

Details provided here are displayed to the user when they are making a connection to our connector and are from another tenant. These details are used on the Consent screen

Test the connection for the connector:

Navigate to https://make.powerapps.com > Data > Custom Connectors

Click the + button against the connector to build a connection to it. When you click, you should be prompted to login to Azure AD

Enter the credentials, if you enter the credentials of an environment other than the current environment, you would be prompted with the following screen

Click Accept and you should have a successful connection object created for this connector.

Note sometimes, after this screen it may display you an error about app registration error. Try again and the next time it succeeds

Moving this custom connector to another environment

Since we added this connector to a solution, simply export the solution as managed solution and import it to the other environment.

Navigate to Custom connectors tab to find the connector listed there

Click the + button to test connection with the connector

If you get an error about invalid client id and secret key,

edit the connector and fill in the security page once again. It will be the same client id and secret key that we had added when creating this connector in the other environment.

Consuming this connector through Power Automate Flows

We are now ready to create a flow and add a step for the operation in our connector.

Choose Manual Trigger of flow

In the Custom tab, you should find our connector

Choose our action

And now provide the requested details in an end user friendly UI

And the result is

Source

The post Building Custom Connectors for Power Apps and Power Automate Flows – Part 2 appeared first on Microsoft Dynamics 365 Blog.

TESTING: Domain is successfully added and lets us navigate to domain "supdvmske.dvmske.com"

Click hereHow to Publish our local Website onto Azure app service created and Deployment center configured

We will demonstrate 2 methods of publishing website from local development machine to azure

1.  Checkin the code from Local to GitHub and Syncing to azure from deployment center
2. downloading publisher and publishing from visual studio to Azure

The post Host Website to azure Web App Part 4 – Setup/configure Custom Domain to azure web App appeared first on Microsoft Dynamics 365 Blog.

Testing: And we have our Website published on Azure, We already configured Deployment center and we can have seamless build from now on.

The post Host Website to azure Web App Part 3 – Publish our local Website onto Azure app service appeared first on Microsoft Dynamics 365 Blog.

CHECK1. Configure Deployment Center for Azure Repo and Azure Pipeline

Deployment center is a Centralised service for all the Deployment methods supported by your app.
It Supports Manual push and sync using FTP, One Drive E.T.C or many external Source Control System like.
Azure Repos

Github

Bitbucket

Local Git

We would be configuring Azure Repos with Azure pipelines

Select Azure Pipelines,
Remember to have a project in Dev Ops: dev.azure.com. I have created a repository before continuing the config

Select Azure pipelines and proceed with selecting  Organization, project, and repository

Verify Information and click on Finish

Once Successfully deployed, we will have Sync Control and can edit the deployment pipeline.

Click Here : Publish Website to azure using deployment center Now once deployment Pipeline as been configured, we can publish our website using Git repository and sync from deployment center or create a profile and publish directly from visual studio

The post Host Website to azure Web App Part 2 – Setup Deployment center Git and Azure Pipelines appeared first on Microsoft Dynamics 365 Blog.

ONE : Create a Web App

Prerequisites : –

• Sign in to your Azure account with active subscription Or create a Traill from  here 
• After login, we will create a resource

• From the Market Place, Select Web APP in popular or search

We will be presented the create Wizard,

1. where we will select a subscription.
2.  Resource Group: This is used to group resource, i.e for my website I can group all resources in “RGDVMSKE”, we can select existing or create a new resource group
3. Name of our  WEB APP, that will be in our URL example SUPDVMKE.azurewebsites.net
4. Publish, we will select it as CODE
5. Runtime Stack: it helps azure to prepare resources for your web app
6. OS: Windows
7. Region: Select the nearest to you
8. Selecting Windows plan: you can create new, I will keep the default created with resource

9. Sku and size: we can select F1 plac=n as shared infrastructure for testing purpose or B1 for minimal DEV purposes, there are Production, isolated with different configuration plans, We can include features here or after configuration i.e custom domain memories, etc

• It will take a few minutes for the deployment to complete.

Click HereTWO: Once Deployment is done GO to Resource to setup Deployment center or enable more features

i.e
Custom Domain -Part 4
Deployment Slots - part 2
AD Authentication
Deployment Center -- part 2
BackUps

Click Here to see how to Setup Deployment Center, Custom Domain or other Azure app services

The post How to Publish or host Website to azure Web App with Azure App Service appeared first on Microsoft Dynamics 365 Blog.

As We all know Microsoft Learn is a learning platform where we practice for any certification by completing some courses.

The best part was while doing the exercise, it provides us with free sandbox for doing practice

-> That will be for 4 hours and I believe that is enough to use practice the section we are learning.
-> In 1 day we can create 10 sandbox

Step 1: Log in to https://docs.microsoft.com/en-us/learn/ and select the course you want to practise

• Navigating to https://docs.microsoft.com/en-us/learn/
• Clicking on any Course you want to practice.

Step 2: Going to exercise and activate Sandbox

• Going to exercise,

• Clicking on activate sandbox

• Review Permission and accept log in

• Sandbox is ready for 4 hours, click on azure portal

• You can see resource group and storage created

• This resource and storage can be used the way you want and check your wor at the end of Exercise

  

The post Learn Azure with a free Sandbox subscription appeared first on Microsoft Dynamics 365 Blog.