Vibe Coding Forem: Syed Kamran

5 Steps to Fix Messy CRM Data in Dynamics 365

Syed Kamran — Mon, 09 Mar 2026 07:33:29 +0000

CRM systems only work well when the data inside them is reliable. Over time, most Dynamics 365 environments start to collect duplicate records, inconsistent fields, and incomplete information. This usually happens when multiple teams enter data in different ways or when records are imported from external sources.

The good news is that Dynamics 365 already provides tools that make cleaning and maintaining CRM data much easier. Here are five practical steps that help bring order back to your CRM.

1. Start by identifying duplicate records

Duplicate accounts, contacts, and leads are one of the most common issues in CRM systems. They often appear when the same customer is added by different users or imported more than once.

In Dynamics 365 you can configure duplicate detection rules. These rules check fields such as email address, phone number, or account name and flag records that appear to be duplicates.

Once the rules are enabled, you can run a duplicate detection job to scan your existing data and generate a list of potential duplicates.

2. Merge duplicate accounts and contacts

After duplicates are identified, the next step is to merge them. Dynamics 365 allows you to merge records while keeping the most accurate data.

For example, if two contact records exist for the same person, you can combine them into one record while choosing which fields to keep. This helps maintain a single source of truth for each customer.

It is a good idea to review important fields such as email, phone, company name, and ownership before completing the merge.

3. Standardize key fields

Messy CRM data often comes from inconsistent data entry. One team may enter company names in full while another uses abbreviations. Phone numbers and addresses can also follow different formats.

Create clear standards for fields such as:

Account names
Email addresses
Phone numbers
Industry categories

Dynamics 365 supports business rules and field validation that help guide users to enter data in a consistent format.

4. Clean incomplete or outdated records

Old or incomplete records reduce the value of your CRM. They also affect reporting and forecasting.

Review records that are missing important information such as contact email, industry, or location. Depending on your process you can update these records, archive them, or remove them if they are no longer relevant.

A periodic data review helps keep your CRM focused on active and meaningful customer information.

5. Prevent the problem from returning

Cleaning data once is helpful. Preventing the issue from returning is even more important.

Some practical steps include:

Enable duplicate detection rules permanently
Restrict certain fields to controlled values
Use data validation where possible
Review imports before they enter the system
Train teams on consistent data entry

These small practices help maintain clean CRM data over time and improve the accuracy of reports, customer insights, and sales pipelines.

Final thoughts

At 3ix, we help businesses review their Dynamics 365 setup, clean CRM data, and build processes that keep data organized going forward. If your team is dealing with duplicate records, inconsistent fields, or unreliable reports, we can help you fix the problem and improve the way your CRM supports your business.

Dynamics 365 Partner - 3ix Consulting

3ix Consulting is emerging as the leading Microsoft Dynamics 365 Implementation Partner for CRM, ERP, and Power Apps Platform.

3ixconsulting.com

How to Integrate Dynamics 365 with External SaaS Tools

Syed Kamran — Tue, 23 Dec 2025 16:52:22 +0000

Many businesses use Dynamics 365 along with tools like Shopify for orders, Stripe for payments, and Zendesk for customer support. When these systems work separately, teams often rely on manual updates or partial information. Integration allows data to move automatically between systems, so everyone works from the same source.

This guide explains how to connect these tools in a clear and practical way.

Start by defining what you want to connect

Begin with one clear use case instead of trying to connect everything at once. Decide what information should appear inside Dynamics 365 and why.

Common starting points include:

Shopify orders appearing in Dynamics 365 Sales
Stripe payments updating customer or invoice records
Zendesk tickets showing under the customer profile

This focus keeps the setup manageable and easier to test.

Choose how the systems will connect

Dynamics 365 connects to external tools using APIs. In most cases, Microsoft’s own tools are used to manage this connection.

The most common options are:

Power Automate for simple workflows and lower data volume
Azure Logic Apps when there are more rules or higher traffic

Both options are Microsoft-supported and suitable for production use.

Set up secure access

Each system must allow secure access to its data. In Dynamics 365, this is done through an Azure app registration that allows records to be created or updated. In Shopify, Stripe, or Zendesk, an API key or access token is generated with limited permissions.

This step ensures that only approved data is shared between systems.

Match data between systems carefully

After the connection is in place, data fields must be mapped correctly so information ends up in the right place.

Typical mappings include:
Customer email to contact email
Order ID to order reference
Payment ID to transaction or invoice record
Ticket number to case record

Good mapping helps avoid duplicate records and missing information.

Test before going live

Testing should reflect real activity. Create a test order, process a payment, or update a support ticket and then confirm the result in Dynamics 365.

Check that:

Records are created or updated correctly
Values match the source system
Duplicate records are not created Only enable the integration for live use after this step.

Why this integration is useful

Once connected:

Sales teams can see order history without opening Shopify
Finance teams can track payments without logging into Stripe
Support teams can view ticket history inside Dynamics 365

This reduces manual work and keeps information consistent across teams.

Conclusion

Integrating Dynamics 365 with external SaaS tools helps teams work with accurate and complete information across sales, finance, and support. When done properly, the setup is reliable, secure, and easier to manage over time.

If you need help planning or implementing a Dynamics 365 integration, 3ix Consulting can support you from initial setup to ongoing improvements.

Reach out to discuss your use case and next steps.
https://3ixconsulting.com/

Deploying Copilot for Finance in Your ERP for Collections and Reporting

Syed Kamran — Mon, 03 Nov 2025 08:18:32 +0000

Finance teams spend hours each week pulling reports, checking overdue payments, and reconciling numbers between systems. Microsoft Copilot for Finance helps make that work faster by connecting directly with your ERP system, like Dynamics 365 Finance or Business Central, and giving you real-time insights right inside tools you already use such as Excel and Outlook.

In this guide, we’ll walk through how to set up Copilot for Finance in your ERP environment and start using it for collections and reporting tasks.

What Copilot for Finance Does

Copilot for Finance is part of Microsoft’s suite of AI-powered assistants built for business users. For finance teams, it connects to your ERP and helps you:

Summarize customer payment history and spot overdue invoices
Draft collection emails in Outlook using live ERP data
Compare actuals versus budget or forecast directly in Excel
Find and explain variances between reports

You don’t need to switch between tools or run manual exports anymore. It’s all right there with simple prompts.

What You’ll Need Before You Start

Before setting it up, make sure your environment is ready:

Licenses – You’ll need Microsoft 365 Copilot or Copilot for Finance licenses assigned to your users.
ERP access – Users should have permission to access Dynamics 365 Finance or Business Central data.
Microsoft 365 setup – Ensure the same users have access to Outlook, Excel, and Teams under the same tenant.
Admin access – You’ll need a Microsoft 365 admin to enable Copilot in your organization.

Once that’s covered, you can start the deployment.

Step-by-Step: Setting Up Copilot for Finance

Let’s go through the main steps to get Copilot for Finance connected with your ERP system.

Step 1: Assign Licenses

Go to the Microsoft 365 Admin Center.
Under Users > Active Users, select the finance users who will use Copilot.
Assign the Copilot for Microsoft 365 or Copilot for Finance license.

Once assigned, users will be able to access Copilot features in Excel, Outlook, and Teams.

Step 2: Check Your ERP Connection

Copilot for Finance works by pulling data directly from Dynamics 365 Finance or Business Central.

In Dynamics 365 Finance, go to System Administration > Setup > Azure Active Directory applications and ensure Microsoft Copilot is registered.
Verify the connection string and permissions so Copilot can read financial data safely.
For Business Central, open Setup and Extensions > Microsoft 365 Connection Setup and confirm the connection is active.

Step 3: Enable Copilot for Finance

From the Microsoft 365 Admin Center, open Settings > Integrated apps.
Select Copilot for Finance and click Deploy.
Follow the prompts to connect to your Dynamics environment. You’ll need to specify your environment URL and approve permissions.

Step 4: Test It in Outlook and Excel

Once deployed, open Outlook or Excel for one of the assigned users.

In Outlook, try opening a customer email and type a prompt like:

“Show this customer’s outstanding invoices.”

Copilot will fetch the data from your ERP and present it in a small panel. You can then ask it to draft a follow-up email for overdue payments.

In Excel, you can use prompts like:

“Summarize sales and collections for October.”
“Explain the variance between actual and forecast for Q3.”

The data comes directly from your ERP system, keeping everything accurate and up to date.

Using Copilot for Collections

Collections are one of the most time-consuming areas in finance. With Copilot connected to your ERP, you can:

View each customer’s payment history without logging into the ERP
Automatically generate polite and professional collection emails based on overdue data
Track follow-ups and mark payments as received

You can even ask Copilot things like:

“Which customers are more than 30 days overdue?”

It will respond with a list pulled straight from your ERP system. This makes it easy to prioritize your outreach and stay on top of receivables.

Using Copilot for Reporting

Reporting becomes much faster once Copilot is set up. Instead of running manual reports, you can:

Ask for financial summaries right inside Excel
Pull real-time data for your monthly close or forecast reviews
Request variance explanations (for example, “Why did operating expenses increase in August?”)

Since the data source is your ERP, the insights are always accurate and current.

Security and Data Considerations

Because finance data is sensitive, Microsoft has built strong safeguards into Copilot. Your data stays within your organization’s Microsoft 365 environment and follows the same security and compliance controls as your existing setup.

Make sure you:

Review user permissions in Dynamics before connecting
Use conditional access and MFA for added protection
Train users on how to handle sensitive financial information responsibly

Tips for Smooth Adoption

**Start small: **Begin with a pilot group in the finance department (for example, accounts receivable).

**Document your use cases: **Note where Copilot adds the most value, such as collections or month-end reporting.

Collect feedback: Ask users what worked well and what could improve before rolling out to the full team.

**Provide quick training: **Short demo sessions or short videos can help everyone get comfortable using prompts effectively.

Wrap-Up

Deploying Copilot for Finance inside Dynamics 365 Finance or Business Central is one of the fastest ways to help finance teams save time and reduce manual work. Once connected, it acts as a smart assistant for your collections, reconciliations, and reporting tasks, all inside tools your team already knows.

Start with a small rollout, focus on key use cases, and let your finance users explore what Copilot can do. Soon you’ll notice fewer manual exports, faster insights, and more time for meaningful analysis.

Would you like me to format this post with short code-style prompts (like Ask Copilot:

"Show overdue invoices by customer"

) and Dev.to markdown styling for headings and sections? It’ll make it blog-ready.

How to Connect Dynamics 365 Pharma CRM to Power BI for Real-Time Sales Dashboards

Syed Kamran — Mon, 22 Sep 2025 08:41:05 +0000

If you work in pharma sales, you know how hard it can be to get a clear picture of your team’s performance. Data often sits in different places: CRM records, Power Apps forms, and spreadsheets. That makes it tough to know which doctors were visited, how many samples were distributed, or what sales numbers look like right now.

This guide will show you how to bring your Dynamics 365 CRM data into Power BI, so you can build real-time sales dashboards. We’ll also see how Power Apps can feed new data into Dynamics 365 and make sure everything flows smoothly.

By the end, you’ll have a working dashboard that updates automatically and gives pharma reps and managers a clear view of sales activity.

What You’ll Need

A Dynamics 365 CRM environment (with pharma sales data or demo data)
A Power Apps license (to build or use custom apps)
A Power BI license (Pro or higher, since we’re connecting live data)
Admin rights to set up connections

Step 1: Prepare Your Data in Dynamics 365

Log into your Dynamics 365 CRM.
Identify the tables (entities) you want, for example:
Accounts (doctors, hospitals, clinics)
Contacts (HCP details)
Opportunities (drug sales opportunities.
Sample Requests (if you track samples through Power Apps)
Make sure these tables have the right fields filled out, since Power BI will read them directly.

Tip: If you’re using a custom Power App for sales reps to log visits or requests, check that the data is writing back to Dynamics 365.

Step 2: Connect Dynamics 365 to Power BI

Open Power BI Desktop.
Click on Get Data → More.
Search for Dataverse (this is the connector for Dynamics 365 data).
Sign in with your Microsoft account.
Select the environment where your pharma CRM data lives.
Choose the tables you want (like Accounts, Opportunities, or your custom pharma entities).
Load them into Power BI.

Step 3: Build Your Sales Dashboard

Once the data loads, you’ll see the tables in the Fields pane.
Drag and drop the following visuals:

Bar chart: Sales by product
Map: HCP visits by location
Line chart: Monthly sales trend
Table: Open opportunities with expected close dates

Rename visuals in plain language, like “Doctor Visits by City” instead of technical terms.

Step 4: Refresh Data Automatically

Save your report and publish it to Power BI Service.
In Power BI Service, go to Datasets → your dataset → Schedule refresh.
Set the refresh frequency (hourly or daily, depending on your needs).
Now, your dashboard will always stay up to date with the latest CRM and Power Apps data.

Step 5: Share with Your Team

In Power BI Service, click Share.
Choose your pharma sales team, managers, or leadership group.
You can also embed the dashboard into Microsoft Teams or even directly inside Dynamics 365 for quick access.

Wrap Up

With these steps, you’ve built a real-time pharma sales dashboard powered by Dynamics 365, Power Apps, and Power BI. This setup removes the guesswork and gives everyone a clear, data-driven view of sales activities.

If you’re working in pharma sales and still juggling spreadsheets or disconnected reports, try setting this up—it will make your team’s decisions faster and smarter.

Looking to set up dashboards like this or integrate Dynamics 365, Power Apps, and Power BI for your pharma sales team?
As a Microsoft Implementation Partner, we help businesses build and connect systems that actually work in the real world. From CRM integrations to custom Power Apps, we can do this and much more for your organization.

Let’s talk about how we can support your team.
https://3ixconsulting.com/contact/

How to Build and Deploy Autonomous Copilot Agents in Dynamics 365 Using Copilot Studio

Syed Kamran — Fri, 15 Aug 2025 09:24:00 +0000

Many companies using Dynamics 365 still deal with slow processes, duplicate work, and delays in follow-ups. Sales teams spend hours updating CRM records. Customer service teams manually route cases. Finance teams chase overdue payments with repetitive emails.

The truth is, these tasks follow predictable patterns that do not require human judgment every time. This is where Autonomous Copilot Agents in Copilot Studio come in. They can run these processes in the background, using your data in Dynamics 365, without constant oversight.

In this guide, we will cover exactly how to set up an autonomous agent that is not just a demo but one you can actually put into production.

What is an Autonomous Copilot Agent

An autonomous Copilot agent is an AI-driven automation tool that can:

Detect specific events or changes in Dynamics 365 data.
Retrieve, process, and combine information from multiple sources.
Execute follow-up actions without manual intervention.
Interact with your other business apps through connectors.

This is not just a chatbot. It can run complete business processes from trigger to completion.

Key pain points they solve

Slow lead response time – New leads sit in the system for hours before being contacted.
Manual case routing – Service requests are assigned manually, which delays resolution.
Inconsistent follow-ups – Some customers get reminders, others do not.
Data entry errors – Repetitive updates lead to mistakes and missing information.

By automating these, you can cut operational delays, improve accuracy, and keep teams focused on high-value work.

What you need before starting

You should have:

A Microsoft 365 account with Copilot Studio access.
An active Dynamics 365 environment (Sales, Customer Service, Finance, or another module where you want to automate).
Security permissions to create and deploy agents.
A documented workflow or process that you want the agent to handle.

Step-by-step: Building and deploying your first agent

Step 1: Access Copilot Studio
From your Microsoft 365 dashboard, open Copilot Studio. Choose "Create new" to start a new agent project.

Step 2: Define the business case
Pick one process to automate. For example, automatically assigning new leads to the right sales rep based on territory.

Step 3: Configure triggers
In the trigger settings, connect to your Dynamics 365 environment and select the event that will start the process, such as “New lead created”.

Step 4: Add actions
Choose the actions the agent should take after the trigger. For a lead assignment process, actions could be:

Retrieve lead details from Dynamics 365.
Match lead to a sales territory table.
Assign the lead to the correct user and notify them in Microsoft Teams.

Step 5: Connect to data sources
Use built-in connectors to pull data from Dynamics 365 entities, Excel files, SharePoint lists, or external systems if required.

Step 6: Apply logic and conditions
Add conditional rules so the agent only runs actions when the criteria are met, avoiding accidental updates.

Step 7: Test in a sandbox
Run the agent in a non-production environment. Check if it performs every step correctly and handles edge cases.

Step 8: Deploy to production
Once validated, publish the agent and make it available to your users. Monitor performance in the first week to ensure stability.

Tips for better results

Start with a high-impact but low-complexity process for your first build.
Document the process before you automate it.
Assign one owner to maintain and improve the agent over time.

What the Results Really Looked Like

A great example of the tangible ROI Generative AI can deliver comes from NVIDIA’s recent AI-powered initiatives in healthcare diagnostics. By integrating AI-driven image analysis into clinical workflows, they helped reduce diagnostic turnaround times by over 50%, leading to faster treatment decisions and cost savings of millions annually for partner hospitals. This shows how Gen AI isn’t just a “future tech” — it’s a proven driver of efficiency and measurable business value.

Final takeaway

Autonomous Copilot Agents in Dynamics 365 let you automate complex, repetitive work using your own data and business rules. They are ideal for reducing delays, increasing accuracy, and freeing up your team’s time. With Copilot Studio, you can configure and deploy them without needing to code from scratch.

Not sure where to start?
We’ll help you get the most out of Dynamics 365.
https://3ixconsulting.com/contact/

Data Migration to Dynamics 365: What Usually Goes Wrong and How to Fix It

Syed Kamran — Thu, 24 Jul 2025 08:28:12 +0000

Migrating data into Dynamics 365 can get tricky fast. You’re not just moving rows from one table to another. You’re dealing with entity relationships, system rules, and tools that behave differently depending on volume and structure.

Here’s what often goes wrong, and how to handle it like a pro.

Entity Mapping Isn’t Always One-to-One

You might think you can map Contact to Contact and Account to Account directly. But once you dig in, things get complex.

Let’s say your source system has contacts linked to multiple account types. In Dynamics, contacts can only have one parent account out of the box. You’ll need to split or redesign the structure.

Also, custom fields often need new option sets or transformations. A "Customer Status" field with values like "Hot," "Cold," or "Warm" might need to be converted to global option set values.

Lookup Fields Can Break Your Import

Dynamics 365 uses GUIDs for lookup fields. You can’t import a contact and just write "ABC Corp" in the parent account field. You need the correct GUID or a way to match it to an existing account.

Best way to do this? Create a reference map ahead of time. Export the Account entity with names and GUIDs. Use Power Query or KingswaySoft to create a lookup table so your import tool knows what goes where.

Choosing the Right Tool Matters

For small loads, you can use the built-in Data Import Wizard or Power Query. But once you hit larger datasets or need automation, you’ll need stronger tools.

KingswaySoft works well for SSIS pipelines. It’s good for scheduled loads, transformation steps, and detailed error logs. Power Platform Dataflows are easier to set up but can struggle with lookups, throttling, and large volumes.

If your source is cloud-based and structured, Azure Data Factory can be useful, but you’ll need more dev experience to set it up properly.

CSV Files Are Not Enough for Complex Relationships

CSV imports work when your data is flat. But if you have nested data, like a list of Contacts each with Activities and related Products, it gets messy.

Instead of trying to cram it all into one file, break it down by entity. Load Accounts first, then Contacts, then related records using their GUIDs. This sequence matters because of lookup dependencies.

Always test with a small batch. See what breaks and adjust the order and format.

Real-World Gotchas

Imported records sometimes fail because of required fields that were added later by other customizations.

Date formats often fail silently. "12/31/2024" in one system may be interpreted as "31/12/2024" or not recognized at all.

You may need to create staging tables if your source system has different naming rules or character limits.

Final Tip

Always log everything. Keep track of failed rows, skipped records, and duplicates. Run your loads in a sandbox first and confirm lookup relationships before going live.

At 3ix Consulting, we help teams navigate these steps with proper tooling, testing, and support so nothing gets lost in the move.

Planning your Dynamics 365 migration? Set it up smart from the start.

Integrating Dynamics 365 with EHR Systems: A Step-by-Step Guide

Syed Kamran — Thu, 12 Jun 2025 08:20:35 +0000

If you’re a healthcare company looking to connect patient records with your CRM, this guide is for you.

Microsoft Dynamics 365 is a powerful tool. But when it’s connected to your Electronic Health Record (EHR) system, it becomes even more valuable. Why? Because your teams can work faster, smarter, and with better data.

Let’s walk through how to integrate an EHR with Dynamics 365.

Why integrate EHR with Dynamics 365?

Most EHRs are great for clinical work, but not built for patient engagement or outreach. Dynamics 365 fills that gap. Together, they allow you to:

Keep patient data in sync across platforms

Track communication and appointments in one place

Automate follow-ups and care plans

Get a 360-degree view of the patient journey

What you’ll need

Before starting, make sure you have:

Access to Microsoft Dynamics 365 (typically Customer Service or Sales module)

Access to your EHR system (e.g., Epic, Cerner, Meditech, or a custom-built one)

A middleware or integration layer — like FHIR API, Azure Logic Apps, or Power Automate

API access credentials for both systems

Developer or IT team support (some steps are technical)

Step-by-step integration process

Step 1: Understand the EHR's API capabilities

Most modern EHRs support FHIR (Fast Healthcare Interoperability Resources) — an industry standard for exchanging healthcare data.

Confirm that your EHR exposes FHIR APIs
Identify endpoints like Patient, Encounter, Observation, etc.

Set up a secure API connection

You’ll need:

OAuth 2.0 authentication (EHRs usually require secure token-based access)
App registration in Azure AD if you're using Microsoft services
Define scopes and permissions for your app (e.g., read/write access to patient data)

Step 3: Use Azure Logic Apps or Power Automate

These tools help bridge Dynamics 365 and the EHR system without needing heavy custom code.

Choose a template (or start from scratch)
Use HTTP connectors to call the EHR API
Use Dynamics 365 connectors to create/update records like Contacts, Cases, or Appointments

Example: When a new patient is added to your EHR, automatically create a new contact in Dynamics 365.

Step 4: Map your data fields

Align the data between both systems. Common mappings include:

EHR Field Dynamics 365 Field
Patient.Name Contact.Full Name
Patient.DOB Contact.Birthdate
Patient.Email Contact.Email Address
Appointment.Date Appointment.Scheduled Date

Make sure data types match and account for optional fields.

Step 5: Test and validate

Start with a test environment. Run a few use cases, such as:

Sync a new patient record
Update a diagnosis or case note
Schedule an appointment and verify in both systems

Check for data delays, formatting issues, or permission errors.

Bonus: Keep it secure

Use encryption for data in transit
Apply role-based access in Dynamics 365
Audit all API activity and log events
Regularly review and update permissions

Final thoughts

EHR and Dynamics 365 don’t have to live in silos. By connecting them, your teams can improve patient communication, reduce manual work, and deliver better care.

At 3iX Consulting, we help healthcare providers design and implement these integrations — securely and efficiently.

Need help connecting your EHR to Dynamics 365?
Let’s talk → 3iX Consulting

How Pharma Sales Teams Can Actually Use Copilot in Dynamics 365

Syed Kamran — Tue, 27 May 2025 16:39:35 +0000

Pharmaceutical sales reps face a tough reality: there are too many leads, too many rules, and never enough time.

If you’re working with a long list of HCPs (healthcare professionals), it’s hard to know where to start. Some might be ready for a deeper conversation, others might be completely cold — but without the right tools, everyone gets treated the same.

That’s where Copilot in Dynamics 365 Sales steps in.

The Real Problem: Sales Teams Are Drowning in Data

Let’s say you have 80 doctors on your list.
You’ve emailed all of them, maybe had a few calls. Now what?

Should you follow up with Dr. Khan who responded last month? Or Dr. Patel who opened your email five times this week but hasn’t replied? This is where most sales reps lose time — trying to guess who’s worth pursuing.

The Fix: Let AI Do the Sorting

Copilot doesn’t just sit in the background. It works with the data you already have in Dynamics 365 and helps you rank your leads.

It looks at behavior — like which HCPs are opening emails, replying quickly, or engaging with marketing content — and calculates a score that says:
“This one is warm. Follow up now.”

No more guessing. No more treating every lead the same.

What Prioritization Looks Like in Action

Let’s say Copilot notices that Dr. Nguyen has opened your last three emails and clicked on a product brochure. Meanwhile, Dr. Silva hasn’t responded in months.

Copilot will move Dr. Nguyen up on your radar. It might even suggest your next move — like booking a call or sending a case study.

You can ask Copilot things like:

“What’s the latest update with Dr. Nguyen?”
And it’ll respond with a summary, including engagement history and recommended next steps.

This helps you spend time where there’s actual potential — and stop chasing dead ends.

Why This Matters in Pharma

In pharma, the sales cycle isn’t quick. It’s relationship-driven. Timing matters.

Copilot helps reps:
Spot the most engaged HCPs
Catch signals like multiple email opens or renewed interest
Resurface old leads that might be warming up again

That means you’re not just more productive — you’re also more strategic.

Managers Benefit Too

While reps get smarter follow-ups, managers get clearer oversight.

They can see which reps need help, which HCPs are slipping through the cracks, and how likely deals are to close — all without waiting for end-of-month reports.

What You Need to Get Started

To use this setup effectively, your team will need:

Dynamics 365 Sales (Enterprise or Premium)
Copilot enabled
Clean, reliable data — because AI is only as good as the inputs

If that sounds like a lot — it doesn’t have to be. That’s where a partner like 3iX Consulting comes in. We help pharma teams get up and running the right way.

Final Thought

Sales teams don’t need more spreadsheets.
They need clarity — who to focus on, when, and why.

Copilot inside Dynamics 365 gives reps that clarity.
Less time guessing. More time selling.

Need help making this work for your team?
3iX Consulting helps pharma sales teams get results with Dynamics 365 and Copilot.

Let’s talk → https://3ixconsulting.com/

Building Custom Extensions for Microsoft 365 Copilot with Teams Toolkit

Syed Kamran — Thu, 08 May 2025 12:36:26 +0000

If you're curious about how to make Microsoft 365 Copilot do more for your team, you're not alone. Copilot is already great at helping people in Word, Excel, and Outlook, but what if it could pull in data from your internal systems or handle tasks that are unique to your business?

That’s where custom extensions come in. And the good news is — you don’t need to start from scratch. Microsoft has made it pretty simple with the Teams Toolkit in Visual Studio Code.

In this guide, I’ll walk you through how to build a basic extension for Copilot, using tools you might already be familiar with. Think of it like giving Copilot a few extra skills, tailored to your team's needs.

First things first — what you need

Before you begin, make sure you have these set up:

Visual Studio Code
The Teams Toolkit extension (you can get it from the Extensions tab in VS Code)
Node.js (version 16 or 18)
A Microsoft 365 developer account with Copilot access

Once that’s done, open VS Code and install the Teams Toolkit. You’ll see a new sidebar pop up, and from there, you can start creating your custom extension.

Create your Copilot extension

Click “Create New App” in the Teams Toolkit sidebar. When it asks what kind of app you want to make, go with “Copilot Agent” and then pick “Declarative Agent”. This is the simpler path because it doesn’t require a lot of backend code.

You’ll then name your project and describe what the extension is supposed to do. For example, maybe you want Copilot to answer questions about internal support tickets or pull in real-time data from your ERP.

If your extension needs access to company systems, you’ll also need to share an OpenAPI spec so Copilot understands what it can talk to and how.

Try it out locally

After setting things up, you can run the project right in VS Code and test how Copilot responds. The toolkit helps you simulate questions, and you can see what kinds of answers Copilot gives based on your instructions.

This is the part where you can tweak things, adjust how it behaves, and make sure it gives the right answers before letting your team use it.

Make it available for your team

Once it’s working the way you want, the next step is to deploy it to your Microsoft 365 environment. This makes your Copilot extension usable for others in your company.

You might need admin permissions for this part, so make sure you're able to publish apps or reach out to someone who can help with that.

Why it’s worth your time

Building a custom Copilot extension might sound like a big task, but with the Teams Toolkit, it’s much easier than you'd expect. You’re basically teaching Copilot how to speak your company’s language and work with your data.

If your team is constantly switching between systems, digging through spreadsheets, or asking the same questions over and over, this kind of extension can save a lot of time.

If you’re exploring Dynamics 365 or want to see how Copilot can fit into your workflows, happy to chat.

Building Your First Plugin for Microsoft 365 Copilot: A Step-by-Step Guide

Syed Kamran — Mon, 28 Apr 2025 07:57:01 +0000

Microsoft 365 Copilot brings AI assistance directly into the tools millions use every day, such as Word, Excel, Outlook, and Teams. With the recent introduction of Copilot Extensibility, developers can now build plugins that extend Copilot’s capabilities using existing APIs, Microsoft Graph, and the Power Platform.
If you're looking to create your first plugin, here’s a practical guide to get you started.

What Are Microsoft 365 Copilot Plugins?

Plugins allow Copilot to interact with external data, services, and workflows. They are based on OpenAI’s plugin standard and enhanced by Microsoft’s security, compliance, and identity management frameworks.

In simple terms, a Copilot plugin is a web API described by an OpenAPI specification, authenticated by Azure Active Directory (Azure AD), and registered through Microsoft’s Developer Portal.

Step 1: Set Up Your Environment

Before you begin:

You need an Azure subscription.
Set up an Azure Active Directory (AAD) App Registration for authentication.
Ensure you have access to the Microsoft 365 Developer Program (free sandbox environments available).

Recommended tools:

Visual Studio Code
Postman (for testing APIs)
ngrok (optional for local development tunneling)

Step 2: Build Your Web API

The heart of a plugin is a RESTful API that Copilot will call. You can build this API using:

.NET
Node.js
Python
Any framework you are comfortable with.

Key things to ensure:

Your API must use OAuth 2.0 authentication via Azure AD.
API responses should be concise and optimized for AI consumption (structured JSON).
Endpoints should perform clear, specific tasks (e.g., getCustomerDetails, fetchSalesReport).

Example endpoint:
GET /customerDetails/{id} Response: { "name": "John Doe", "email": "john@example.com", "purchaseHistory": ["Product A", "Product B"] }

Step 3: Create the OpenAPI Specification

You must define your API in an OpenAPI (Swagger) 3.0 format.
This file describes:

Available endpoints
Request/response formats
Authentication methods

Microsoft requires minimalistic OpenAPI documents to keep interactions fast and predictable for Copilot.

Step 4: Register Your Plugin

Use the Microsoft 365 Developer Portal to register your plugin:

Upload your OpenAPI specification.
Connect the plugin to your AAD app for authentication.
Define permissions carefully (the fewer, the better).
Test the endpoints from the portal itself. Once registered, the plugin becomes available within the Microsoft 365 ecosystem where users can install and use it with Copilot.

Step 5: Test with Copilot

After successful registration:

Install the plugin in your sandbox environment.
Test it across different Microsoft 365 apps.
Ensure that Copilot understands your plugin’s responses and properly integrates them into conversations or task automation.

Testing Tip:
Keep your API responses clean and descriptive, as Copilot depends on accurate information to respond intelligently.

Final Notes

Plugins for Microsoft 365 Copilot open a new way for developers to integrate business logic into daily productivity workflows. Microsoft handles identity, security, and compliance, so developers can focus on building useful APIs that Copilot can use to serve users better.

If you’re familiar with building APIs and working with Azure, you already have most of the skills needed to build impactful plugins.

How to Integrate Microsoft Dynamics 365 with Power Automate

Syed Kamran — Thu, 27 Mar 2025 08:13:59 +0000

If you've ever felt like you're spending way too much time on repetitive tasks in Dynamics 365, you're not alone. Updating records, sending follow-up emails, creating tasks—it adds up fast. But what if you could set it up once and let it run on autopilot?

That’s exactly what Power Automate does. It takes care of the boring stuff so you can focus on what actually matters.

New to Power Automate? No worries, I’ll walk you through it step by step. And if you've already used it, stick around—you might pick up a few tricks to make your workflows even better.

Why Use Power Automate with Dynamics 365?

Power Automate connects Dynamics 365 with hundreds of applications, letting you trigger workflows based on data changes, schedule processes, or even call external APIs. Instead of manually updating records or sending emails, you can let Power Automate handle it in the background.

Example Use Case:

A sales team wants an automatic email sent to customers whenever a new lead is added in Dynamics 365. With Power Automate, this takes just a few minutes to set up—no, coding required.

Step 1: Setting Up Power Automate for Dynamics 365

1. Access Power Automate

Go to Power Automate and sign in with your Microsoft account.

Click Create to start a new flow.

2. Choose a Trigger

Click Automated cloud flow to start a flow triggered by an event in Dynamics 365.

Search for Microsoft Dataverse (formerly Common Data Service) as the trigger source.

Select When a row is added, modified, or deleted.

Choose your Dynamics 365 environment and entity (e.g., Leads).

3. Define the Trigger Condition

If you want the flow to run only when a new lead is created, set the Change Type to Added.

To filter leads (e.g., only from a certain region), use Filter Rows with OData queries:'

address1_stateorprovince eq 'Texas'

Step 2: Add Actions to the Flow

1. Send an Email

Click + New step and select Outlook 365 - Send an Email.

Set the recipient to the email field from the lead record.

Customize the subject and body using dynamic content:

Subject: Welcome, [Full Name]!
Body: Hi [First Name], thanks for your interest. We'll reach out soon!

2. Create a Task in Dynamics 365

Add another step and select Microsoft Dataverse - Add a New Row.

Choose the Task table and set:

Subject: Follow-up with [Lead Name]

Owner: Assign to a sales rep

Due Date: Date of lead creation + 3 days

Step 3: Test and Deploy

1. Test the Flow

Click Test and choose Manually or Automatically.

Add a test lead in Dynamics 365 to see if the flow works.

If needed, check the Run History for debugging.

2. Enable the Flow

Once satisfied, turn on the flow and monitor its performance in Power Automate analytics.

Advanced Customization

Calling an External API from Dynamics 365

You can extend the flow by calling an external API. For example, to validate email addresses using a third-party service:

GET https://api.emailvalidation.com/validate?email=[Lead Email]
Headers: {
  "Authorization": "Bearer YOUR_API_KEY"
}

If the API returns valid = false, send a notification to the sales team instead of an email to the lead.

Using Power Automate Expressions

Power Automate allows expressions to modify data dynamically. Example:

concat('Welcome, ', triggerOutputs()?['body/firstname'], '!')

This ensures a personalized message based on the lead’s first name.

Troubleshooting Common Issues

1. Flow Not Triggering?

Check if the Dataverse trigger has correct permissions.

Make sure the flow is enabled and connected to the right environment.

2. Duplicate Emails Being Sent?

Use Scope and Condition actions to prevent multiple triggers.

3. API Calls Failing?

Verify the API key and endpoint.

Test using Postman before integrating into Power Automate.

Final Thoughts

With Power Automate, integrating Dynamics 365 with other tools becomes straightforward. You can automate customer follow-ups, trigger business processes, and reduce manual data entry, all without writing extensive code. As you explore more, you’ll find even better ways to streamline your workflows.

How to Automate Lead Scoring in D365 Sales

Syed Kamran — Thu, 20 Mar 2025 08:10:32 +0000

Lead scoring helps sales teams focus on the most promising prospects by ranking leads based on their likelihood to convert. Automating this process in D365 Sales ensures faster decision-making, better resource allocation, and improved sales outcomes. Here’s a step-by-step guide to setting up automated lead scoring.

Step 1: Define Lead Scoring Criteria

Before setting up automation, decide what factors indicate a high-quality lead. These may include:

Demographics (Industry, Company Size, Job Role)
Engagement (Email Opens, Website Visits, Webinar Attendance)
Actions Taken (Demo Requests, Form Submissions, Free Trial Sign-Ups)
Deal Potential (Budget, Decision-Making Power, Urgency)

Each of these factors should have a point value assigned based on importance

Step 2: Set Up a Lead Scoring Model

D365 Sales allows you to build a scoring model to rank leads automatically.

*Go to the Lead Scoring Module *– Navigate to the Sales Insights settings.
Create a New Lead Scoring Model – Click on “New Model” and define your scoring parameters.
Assign Point Values – Allocate scores based on behaviors and engagement levels (e.g., +10 for opening an email, +20 for scheduling a demo).
Set Score Thresholds – Decide at what score a lead should be classified as warm, hot, or ready for sales.

Step 3: Automate Lead Qualification

With scoring in place, you can set automation rules to categorize leads based on their score.

Use Workflows – Create workflows that update lead status when a score crosses a threshold.
Trigger Notifications – Set up automatic alerts to notify sales reps when a high-score lead is ready for follow-up.
Assign Leads Automatically – Route leads to the right sales reps based on their score and region.

Step 4: Integrate with Other Tools

To enhance lead scoring, connect D365 Sales with:

Marketing Automation (e.g., emails, social media engagement tracking)
Power BI for deeper insights into lead behavior
LinkedIn Sales Navigator for additional data enrichment

Step 5: Monitor and Optimize

Once your lead scoring model is live, regularly analyze its effectiveness.

Check Conversion Rates – Are high-score leads converting at a better rate?
Adjust Scoring Criteria – Fine-tune weights based on real data.
Get Feedback from Sales Teams – Ensure the model aligns with real-world sales experiences.

Final Thoughts

Automating lead scoring removes guesswork and allows sales teams to focus on the best opportunities. By setting clear criteria, assigning scores, and integrating automation, businesses can improve efficiency and close deals faster.

Need help setting up lead scoring?
Let’s talk!