New Project Team Experience (OneGrid) in Project Operations

November 5, 2026November 5, 2026 priyeshwagh777 Project Operations Dataverse, Dynamics 365, Power Platform Admin Center, Project Operations

If you’ve been using the Team tab on a Project in Project Operations, there’s a new experience you can switch on now – the Team Member grid can use the Power Apps OneGrid control, the same modern grid you are already seeing across other areas of the app.

Here’s how to enable it and what changes on the Team tab – before and after –

Enable the Feature

In Project Operations, change the area to Settings and open Parameters. Open the Parameter record and drop down Feature Control. Look for Enable OneGrid for Team Member – notice it doesn’t have a check mark yet.
You’ll be asked to confirm. As the message says, the Power Apps OneGrid control will now be used for the Team Member grid on the Project form. Click Enable. Note: once enabled, the option no longer appears in the Feature Control list, so do this on a Sandbox first and see how your users like it.

Before

Here’s how the Team tab looked on my project before enabling the feature – a regular subgrid with + New, Refresh and Flow.
And when I expand a team member, I see the tasks they are assigned to. Selecting the row gives me Generate Requirement and Subcontracting Options.

After

Now, on the same project, the Team tab uses the new grid. You get checkboxes to select rows, the Bookable Resource, Role, Resourcing Unit and Position are now clickable links, and there’s a new Add Existing Project Team button right next to + New. At the bottom, you also get a Rows count.
Expanding a team member now opens a proper nested grid for the task assignments – with its own checkboxes, links to the Task, Bookable Resource and Role, an icon to open each assignment record and a Rows count of its own. When I select the team member, Generate Requirement and Subcontracting Options are still right there, and the footer shows how many rows are selected.

So nothing changes in how you staff your project – it’s the same actions, just in a grid that’s easier to work with, especially on projects with larger teams.

Hope this was helpful!

Here are some more Project Operations posts you want to check out –

And some popular Power Automate posts –

Thank you!

Work with your Dynamics 365 CE data from Copilot using Dataverse MCP

October 20, 2026October 20, 2026 priyeshwagh777 Dataverse, microsoft copilot Dataverse, Dataverse MCP, Dynamics 365, MCP, Power Platform

If you are already using Copilot via an M365 Copilot license and it is helping you in productivity already – you might want to take it a step further and enable it to also bring in your Dynamics 365 CE data together – be in Project Operations, Field Service, Sales, Customer Service etc.

Examples: Copilot is helping me with my emails, SharePoint files – summarizing and triaging information. But have to still log into Dynamics 365 to get work done. Well, by default this is not enabled for organizations and ready to use but your Admin team can help you enable this.
Make sure the users who will use this have an M365 Copilot license assigned to them and you have the right Admin privileges across M365, Power Platform Admin Center, Azure and Teams Development Portal.

Let’s see it how and make it work!

Step 1 – Register an App in Microsoft Entra

Give you have the right access to Azure with permissions, you need to create a new App Registration and follow the steps along –

Add a new App Registration in Azure Portal.
Then, enter the Name and select Web in the Redirect URI [https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect]
Once the App is registered. Save the App Registration ID and Tenant ID.
Then, navigate to the Certificates & secrets. And add a new Client Secret there.
Now, store the value before you refresh the page. You’ll need the Secret Value.
Now, go to API Permissions as below.
Select Dynamics 365 CRM and mcp.tools as Delegated access.
Then, grant the permissions.

And finally, Grant the permissions as below.

And check that the Permission is granted.

Step 2 – Allow the App on the Dataverse MCP Server using Power Platform Admin Center

Given you have Dynamics 365 Admin privileges, navigate to Power Platform Admin Center. Navigate to your environment and look for Features under Settings.
Then, navigate to Data Model Context Protocol and make sure Allow MCP clients to interact with Dataverse MCP server (GA version) is enabled. [Based on when you are reading this blog, the mention of version might change]

Click on Advanced Settings which will take you in Dynamics CE to.
Click on new MCP Client.
You already have the Application ID from Azure’s App Registration. Copy it as you’ll need it here.
Then, enter register the App Registration as an MCP Client here. Give it a suitable name, but also make sure to add prefix yourself. I just added “new_”
Set Is Enabled to Yes. Save the record.

This is set now.

Step 3 – Register the OAuth Connection in Teams Developer Portal

You need to register the OAuth Endpoint here.

Navigate to Tools as shown and then select OAuth Registration.
Register a new client. This will be similar to App Registrations you’ve used to doing before. Just that the information is to be borrowed from the App Registration on Azure we did above.
Click Register client.
Fill in the details as asked
Once created, copy the Reg ID. You’ll need this in the Reference ID asked in the Microsoft Copilot Portal below.

Here, you are now ready to consume this to create a new Custom Connector in M365 Admin Center’s Copilot area. Let’s see ahead.

Step 3 – Create the Connector in Microsoft 365 Admin Center

Given that you are an M365 Global Administrator, you need to now deploy this as a Custom Connector in M365 Admin Center under Copilot –

Go to M365 Admin Center [https://admin.cloud.microsoft/]. Then, expand Copilot on the left hand pane and look for Connectors.
Register your Connector. Enter the name and the info like the URL, and Description which are mandatory.
Further, add more details as asked and the copied Reference ID from Teams Developer Portal app is to be pasted here. Refer Step 3 and point #3 from above.
Now, click Authorize.
Then, click Authorize again. It should go through and show as below. Then click, Create at the bottom.

Once created, it’ll be available like this.

Now, let’s roll it out to the users!

Step 5 – Roll it out to your Users

Now, let’s roll it out to the users. Follow the steps below –

Navigate to the Copilot area in the the left hand pane. Look for Connectors, under Your Connections, wait for a bit for the list to refresh. You’ll find yours there. Click on the three dots and then click Add Staging.

It takes a few mins for this to be available to the selected users.

Step 6 – Connect from Copilot Chat

Now, let’s test!

In your Copilot Chat, look for the gear icon next to your profile, then navigate to Settings.
Look for Sources, you’ll see list of Connectors available.
Search for your Connector there and it’ll show up. Once you find it, click Connect on the Connector. It’ll authenticate you in.
Click Continue and you should be connected in a moment.
Then, you can also look at what tools are available for you to use.

And you are all set. Let’s test.

Query your CRM data here!

Now, you can start by querying your CRM data here – just ask anything from the environment and validate if it is returning correct answers. Involve System Admins and the ones who deployed if you need to further fine tune your Connector.

Hope this was helpful!

Here are some more Dataverse and Copilot posts you want to check out –

And some popular Power Automate posts –

Thank you!

AI in Dynamics 365 CE Applications: Transforming Solution Architecting

August 31, 2026August 31, 2026 priyeshwagh777 AI Thought Leadership agentic development, ai in business applications, Claude, Dynamics 365, microsoft copilot

Given my 12.5 years in the industry at this point – where I started my journey from Dynamics CRM 2013 online (and having dealt with some D365 CRM 4.0 on-prem along the way too) – I’ve come a long way from changing XML for SiteMaps to make sure the Calendar is set right for new orgs – features in D365 CRM got added and many features kept getting deprecated [Although the later is less than the former].

The only help I get and also which I offered was treacherous hours and hours spent in making sure the. ‘customer experience’ is top notch as much as the quality of my solutioning.
Now, sitting in later half of 2026 and putting even the Solution Architecting years behind me – I look back in time and gauge what has changed really?

Well, fundamentally things remain the same –

Set up new environments
Implement C# plugins and JS for custom logic
Configure roles, System Settings
Configure behind the scenes for applications like Project Operations, Field Service, Customer Service etc.
Migrate and deploy solutions between environments

…and so on.

But, the medium of doing all the above has changed. That definitely has!

With advent of AI tools – Copilot, Claude, ChatGPT, disparate configuration pieces are more connected to each other and to the Developer / Solution Architect sitting in front of the screen on a random Tuesday midnight.

So from a bird’s eye view of things – here’s what is more cohesive, AI-powered and in control which I plan to write further in this series and connect it all together as we sunset 2026 in these relatively newer Agentic development years.

Metadata, Configuration: Dataverse MCP on your AI tools like Claude.
CI/CD: Power Platform Pipelines, Azure DevOps
C# Plugins and Code: Claude Code, GitHub Copilot
End User Guides / Documentation: Claude Design, Figma, Copilot in Office Apps

So in the new few weeks and month, as AI continues to ever-evolve, I’ll share with my audience a framework of bringing together all the applications together with AI to deliver the same high-quality CE applications in an agentic-way.

And it doesn’t stop there – probably years after, there would be something else to replace it. But till then, this areas continue to evolve and take shape bringing from my experience and feedback from the teams and customers I work with in this remaining decade.

Hope this was helpful!

Here are some Power Automate posts you want to check out –

Thank you

Price Override in Project Operations | Part 1 [Understanding Change Amount effect]

January 31, 2026January 31, 2026 priyeshwagh777 Project Operations Dynamics 365, dynamics 365 erp, power apps, Project Operations

So, often times if you are working on Project Contracts, you must have encountered this button which creates a separate Price List for the Quote itself – Project Contract Price List Defaulting Behavior in Project Operations

But here’s how to track and find what happens to these Price Lists and what Price Override levels are –

Creating Price Overrides

Here’ where you can find the Prices to be overridden on a Price List level –
Now, when a new Quick Create form is created, you can fill in the details for either the new Price or the % and the Scope.
Now, when you add the Price Per Unit, also notice that there’s a Scope field as well. Notice the types of records for the Scope defines at what level should this take effect.
Let’s select an Account and save.
Now when I save the record, notice that the Price is added differently.

So, let me demystify this Part 2 of this post here: Price Override in Project Operations | Part 2 [Understanding Change Amount effect]

Hope this was helpful!

Here are some Power Automate posts you want to check out –

Thank you!

Setting up Codex with Power Platform MCP Server

November 26, 2025November 26, 2025 priyeshwagh777 Power Automate, Power Platform, Power Platform Admin Center chatgpt, codex, Dynamics 365, mcp server, Power Platform, power platform mcp

Amongst available AI clients available, Codex is well-known by ChatGPT and here’s how you can use to configure with Power Platform MCP Server.

Install Codex on VS Code

One of the first things to do is to install Codex as an extension in Visual Studio Code –

Look for the below extension and you should see a ChatGPT icon.
Once this is installed, go to Extensions and you can sign in with your GitHub Pro account.
It’ll open up a Sign-in page and you’ll need to enter your credentials.
Make sure you open a Folder in VS Code and also ensure npm is installed by running this command in terminal ‘npm -v‘.
Next, before you configure the TOML file – make sure you are having powerplatform-mcp installed locally and then configure the TOML file for Codex.

Downloading Power Platform MCP locally and connecting to the MCP

Now that Codex is installed and NPM is installed as well. Let’s first download Power Platform MCP first and then connect it to the Power Platform MCP environment –

Let’s check if PowerPlatform-MCP is already installed or not by checking its version number.
Below, it says that it didn’t find zsh, means powerplatform-mcp is not installed locally.
Because I use a Mac, I can do so using Homebrew. You can check alternatively on doing this using Windows and downloading using Powershell.
In case you face permission issues on the device, you can just run the below command –
“sudo npm install -g powerplatform-mcp” and you should see the packages getting downloaded successfully.
Now, go ahead and configure the Toml file.
Then, in the TOML file, you can enter the configuration like so –
And when you try to query in Codex, you’ll see the results come through in the form of answers.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Time Entry Calendar in Project Operations

August 31, 2025August 31, 2025 priyeshwagh777 CRM with .NET Web Applications Dynamics 365, dynamics 365 project operations, Power Platform, Project Operations, time entry calendar

If you have been used to doing Time Entries daily on the classic Time Entry grid and that has been a habit for quite some time, you might not realize that it is slower and inefficient to do, just because you got used to it now.
So, here’s Time Entry calendar view which is better way to visualize and do Time Entries! This is in Preview as of the day of writing this post.

Enable Time Entry Calendar View

Here’s how you can turn on your Time Entry Calendar from Project Operations’ Settings

Navigate to Settings Area in Project Operations Model-Driven app.
Then drop down form Features to find the Time Entry Calendar listed.
Click on it to turn it on. It’ll ask for confirmation, it ask describes what it does.

How Time Entry Calendar works?

Here’s how Time Entry Calendar feature works when you want to do Time Entries.

Now when you navigate to the Time Entries from My Work (or wherever you have put it), you’ll see this new option in My Work called as Time Entry Calendar, while you existing Time Entry section still exists as is.
When it loads, you can see the Time Entries now appear like how allocations appear on your Schedule Board, gives you a better way to visualize Time Entries to be done and and most importantly, select the Time for the Time Entry.
You can visualize Daily, Weekly and Monthly.
You can even click on the Time you want to make Time Entry on and the window pane will let you drill down to the Task level on the Project which you want to make Time Entry on.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Project Task Progress Update in Project Operations & Mark Task as Completed

March 29, 2025March 29, 2025 priyeshwagh777 Project Operations Dynamics 365, Project Operations, project progress

Up until now, you had to do Time Entries to mark a Project Task as completed. But, this makes difficult to gauge the progress of the project in actuality as some tasks might need to be marked as completed without having to do remaining Time Entries on them.

Here’s when marking Project Task as Completed comes in handy.

Default Behavior for Project Tasks in Project Operations

By default, you won’t be able to edit the % of the task in the Project Task Grid –

Till now, you are able to directly mark a Task as complete by using the below option –
And it’ll mark the task as Completed to 100%. But, when hover over the % completed, it’ll say that it’s a read-only and can’t be edited to put your custom % in there.
So, let’s see how this feature will let you edit the % complete to your desired number.

Enable marking Project Tasks as completed

In Project Parameters, you can find the Feature to mark Project Task as completed –

Drop down on the Feature Control and you’ll see that Task C

Mark Project Tasks as completed

When you enable this, you’ll see the below on the Project –

The Project form will have the field to allow Project Tasks to have custom progress % option.
Once you do this, you’ll then be able to hover over the Project Task and enter the % you desire.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Recycle Bin in Dynamics 365 CRM | [Preview]

August 11, 2024 priyeshwagh777 D365 Admin Center, Power Platform Admin Center Dataverse, Dynamics 365, power apps, Power Automate, Power Platform, power platform ad, Power Platform Admin Center, recycle bin for dataverse, restore in dynamics crm, restore records

Now, you can retrieve deleted records up to 30 days in Dynamics 365 CRM /. CE apps.
Here’s how you turn this feature on!

Enable Recycle Bin

Here’s how you can enable this given you have the correct Dynamics 365 System Administrator privileges –

Go to the Environment’s Settings in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)
Now, expand Product section and go to the Features option.
When you scroll to the bottom, you’ll see Recycle Bin option as a feature. At the time of this blog post, the feature is in Preview – Hence, this is not recommended for production purposes yet.
By default, it’s turned Off.
Once you flick the switch, you’ll be asked for number of days the data has to be retained for. I’ll enter 30 here and then scroll to the bottom and save the setting.
Once saved, you can go to your environment and test this on a sample record. See the section next.

Deleted Records

Now, since this is enabled and post that when you delete records, here’s how you can find them for the number of days you’ve configured Recycle Bin for –

For example, this is the Account record you want to delete.
Go to the View Deleted Records section in the in your environment’s Settings area.
You’ll see the Deleted records which you can select and choose to Restore.
Confirm.
Upon Restoring, they’ll appear where they were originally supposed to exist.

Because this feature is still in Preview, here’s Microsoft’s Documentation on the same with listing of some known issues as well – https://learn.microsoft.com/en-gb/power-platform/admin/restore-deleted-table-records?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Create a Custom Connector For Power Automate & Power Apps

July 15, 2024 priyeshwagh777 Azure Functions, Customizations, Microsoft Azure, Microsoft PowerApps, Power Automate, Power Platform azure, custom connector, Dynamics 365, Microsoft Azure, power apps, Power Automate, Power Platform

One of the most important qualities of extending capabilities of any platform is being able to add Custom code and make it available to wider use cases.

In this case, it’s a custom code that is encompassed in a Custom Connector in Power Platform and made available to Power Automate or Power Platform.

Use Case

The purpose of my custom connector is to call my hosted custom code in Power Automate or Power Apps.

For this example, I’ve created a simple Azure Function that just returns a value – just to test the working of the Custom Connector. Of course, your use case is to be able to connect to the hosted app, expect it to process the business logic which you intend to do and return back the results.
So, in my case – my Azure Function will simply greet the name passed to it.

See the Postman test below –

Now, let’s make a Custom Connector that will execute this Azure Function in your Power Automate.

Create Custom Connector in Power Apps / Power Automate

You can either make the Custom Connector from the Power Automate portal or the Power Apps Maker portal, both are the same things. Let’s see this example from Power Apps portal –

In this use case, I’m in a Solution in Power Apps / Power Automate. Open the one in your case since you can’t create a Custom Connector from outside a Solution any longer.
Now you can drop down from New and see in Automation menu that you can create a Custom Connector
Now, you’ll be required to enter the name of the Connector itself and other details like a PNG icon for it, Description etc.
Now, below is the info that I filled in. I’m calling it Data Transporter and have selected an Icon which should make me easy to recognize my connector in Power Automate and Power Apps and enter enter the details of my hosted Azure Function which is authenticated using an API Key.
So, here’s what my info looks like –
Now, when I click on Security after filling all the info, the type of Authentication I used in this case if API Key, yours could be different depending on what your custom application is configured to work with –
It’ll ask you to fill in the information so that it appears as parameters to fill in for the Custom Connector when the end user will work on their Flows/Apps.
The info I’m choosing to fill is this – I’m giving a name to the parameter to indicate what info is required. The actual parameter name required by the Azure Function, in this case – it’s ‘code’ and since I need to pass the API key in Query string, I’ve selected Query instead of Header.
When you go to the next part, i.e. Definition, make sure you also give a Name to the Custom Connector already. Before your lose the info you’ve already entered. Make sure you also click on Create Connector

Once you click on Create connector, it’ll create it in a few moments.
Now, since you are aware of Triggers and Actions from using Power Automate – in this use case, my Custom Connector is designed to be an Action i.e. when called/used in Power Automate, it’ll simply perform the operation it’s designed to do.
Hence, I’m selecting an Action here.
When I select New Action from the left hand pane, it’ll open up information for me to fill out to describe the Action.
Now, since this will appear as a listed item in Actions in my Power Automate connector, I’m filling in this info (and we can check later how it appears).

Next, I’ll click on + Import from sample as it’ll give me a place to enter a sample for the request to call my hosted Azure Function.
Next, I’ll pass these values as I did in Postman to create the sample. Once done, I can click on Import.
When I import, I’ll the request parameters set in the Custom Connector based on the sample I entered.
Next, I’ll scroll down to ensure that all validations are perfect and I needn’t fix anything.
Next, I’ll skip AI Plugins step and also the Code step since I want to keep this example concise and to the scope of the hosted Azure Function only.

And this is skipped too –
Now, the final step is to Test the Custom Connector. The Editor will ask you to Update connector before you can Test. Then, in order to begin testing – you’ll need to first create a Connection using New Connection button as shown below.
When you click on New Connection, you’ll be taken to a new tab to enter the API key which you created as parameter in the initial setup of this Connector. See #7 above. Enter the API key you have which works for this hosted app and then click Create connection.
Next, in case the Connection doesn’t appear, click Refresh button once.
Once you refresh, you should see your Connection come up and selected.
Now, next step is to test the Custom Connector itself. Enter the values that you wish to test for and click Test operation.
You’ll see the test results based on what the hosted code is supposed to perform.
In my case, it was easy as it just greets the name entered.

And your Custom Connector is now ready to be used!

Consuming Custom Connector

Now, let’s see how you can use the Customer Connector in Power Automate in order to perform the operation in your Flows –

Once in Power Automate, look for the Custom tab in the Action selector.
Then, you can see the Action you defined in your Connector Definition steps above.
Since you need to authenticate using the API key you have, the create Connection step will ask you this info and you can give the name of the Connection.
Pass the value you want to pass as data.
Finally, you can just save and test the Flow itself and look for your Outputs.

And that’s how you can have a Custom Connector for your custom app/service your have created. I’ll soon write about other aspects of Custom Connector which I wasn’t able to cover in this blog.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Create your first custom Copilot for Customer Service Hub – Part 2 | Authentication

July 10, 2024 priyeshwagh777 microsoft copilot ai, copilot, custom copilot, customer service, Dynamics 365, microsoft, microsoft copilot, Power Platform

Now, you must have created your own Copilot to be deployed for the Customer Service Hub. If not, here’s the link to Part 1 of this blog – Create your first custom Copilot for Customer Service Hub – Part 1

Configure User Authentication with Microsoft Entra ID

Here’s how you can configure the User Authentication with Microsoft’s Entra ID for your Copilot to be authenticated with –

Go to the Azure Portal [https://portal.azure.com/], then given the appropriate permissions your might have, you should be able to create an App Registration
Now, create on New Registration –
Now, give it a suitable name so that you can identify that the purpose of this App Registration is for Copilot. Select multi-tenant, leave Redirect URI blank and click on Register.
Once ready, go to Authentication and then click to add Platform.
In the platform selection, click on Web.
Now, enter the URIs – First, enter the first URI, make sure to select Access tokens and ID tokens in Implicit grant and hybrid flows section and then click Configure.

https://token.botframework.com/.auth/web/redirect https://europe.token.botframework.com/.auth/web/redirect
Then, go ahead and add the Second URI from the main screen itself. Then, click Save and refresh the page once.
Now that both the URIs are added, click on the configuration link to consider both the links for configuration.
Now, you’ll be taken to this pane where you can click
Now, both the URIs will appear here.
Next, generate Client ID and Client Secret as you’ll need these details too –

Set Copilot Authentication to use Custom Authentication

Going back to the Copilot itself, set the Authentication you just created in the Azure Portal –

Go to Settings on the Copilot to use the Custom Authentication.
Go to Security section and then select Authentication.
Select Authenticate manually and then enter the details as shown below. Enter the Client ID and Secret which you must’ve saved before.
Next, come back to Copilot Settings and in Security, go to Settings and then look for Web channel security.
Once you open it, you’ll find that the Secured Access is disabled. Go ahead and enable it.
It takes up to 2 hours for it to take effect. Till then, old settings apply.
Finally, in Channels, select Customer Service Hub so that you can connect to the Customer Service Hub.
On the right hand side pane which opens up, you’ll see that this is not connected. Click the Connect button.
It connects to Customer Service Omnichannel in a few moments.