A machine stops in the middle of a shift. The technician standing beside it can see the problem, but the person with the deepest knowledge of that machine may be hundreds or thousands of kilometers away. Traditionally, solving that problem could involve telephone calls, photographs, emails, unclear descriptions, repeated questions, or eventually sending a specialist to the site. The challenge is not necessarily that expertise does not exist. The challenge is getting that expertise to the place where the work is happening. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Remote Assist in plain English and explores how frontline workers can connect with remote experts through live video, visual guidance, Microsoft Teams, mobile devices, mixed reality, and connected Dynamics 365 processes. We look at how Remote Assist supports field service, manufacturing, maintenance, inspections, troubleshooting, training, remote collaboration, Microsoft Teams, Dynamics 365 Field Service, Microsoft 365 identity and security, and mixed reality scenarios. The central idea is simple: instead of trying to describe a physical problem to someone who cannot see it, let the expert see what the frontline worker sees.

THE PROBLEM WITH REMOTE TECHNICAL SUPPORT
Many frontline jobs happen far away from a desk. Maintenance employees work beside production equipment. Field technicians visit customer locations. Inspectors examine physical components. Engineers install machinery. Service teams troubleshoot equipment in warehouses, factories, offices, hospitals, or other facilities. When something unexpected happens, the employee on site can see the problem directly. They might hear an unusual sound. They might notice a loose cable. A warning light might appear. A component may not fit correctly. The difficulty begins when the employee needs help from someone who is somewhere else. The remote expert cannot initially see any of those details. The technician has to translate a physical situation into words. That translation creates opportunities for misunderstanding. 

WHY PHONE SUPPORT HAS LIMITATIONS
Imagine calling an expert and saying: "There's something wrong with the connector at the back." The sentence makes perfect sense to the technician standing beside the machine. But the remote expert immediately has several questions. Which connector? Which side of the machine? What is connected to it? What does the surrounding equipment look like? Is there visible damage? Is another component positioned incorrectly? The technician describes the situation. The expert tries to reconstruct the machine mentally. Both people may eventually understand each other, but valuable time can disappear simply establishing which physical object they are discussing. Dynamics 365 Remote Assist was designed to reduce that gap by creating a shared visual context.

PHOTOS ARE USEFUL BUT STATIC
Photographs improve remote support because the expert can finally see something. But a photograph represents one moment from one angle. The expert might reply: "Can you send another picture from the side?" The technician takes another photograph. Then the expert needs a close-up. Another photograph. Then they need to understand where that component sits relative to another part. Another photograph. Meanwhile, the technician may have moved, removed another panel, or discovered a different problem. Live video changes this interaction because the expert can ask the technician to move the camera immediately. Instead of exchanging snapshots of the problem, both people can explore the physical environment together.

WHAT IS DYNAMICS 365 REMOTE ASSIST?
Dynamics 365 Remote Assist is a Microsoft application designed to connect a frontline worker with a remote expert while keeping the conversation focused on the physical work being performed. The worker can share live video of the equipment, environment, or problem. The remote expert sees the same physical scene and can provide guidance while the technician remains beside the equipment. The worker might use a supported smartphone or tablet. For appropriate hands-free scenarios, supported mixed reality headsets can provide another experience. The objective is not to make the remote expert physically present. It is to give that expert enough visual context to provide more useful assistance without immediately traveling to the location. ㅤ

LIVE VIDEO CHANGES THE SUPPORT CONVERSATION
Imagine an expert sitting in a central support office. Without Remote Assist, they might receive a service ticket containing several sentences and a photograph. They need to interpret the problem from that limited information. With Remote Assist, the worker's camera becomes a window into the work environment. The technician can show the complete machine. Then the control panel. Then the component producing the problem. The expert can ask the technician to move closer, change the viewing angle, show a label, follow a cable, or inspect another component. The conversation becomes interactive. The expert no longer needs to imagine the physical environment entirely from a written description.

USING REMOTE ASSIST ON MOBILE DEVICES Not every remote support scenario requires mixed reality hardware. Supported smartphones and tablets can provide a practical option for many everyday service situations. A field technician can take out a device, contact an expert, show the equipment, receive guidance, and continue working. This makes Remote Assist relevant to organizations that want visual remote support without deploying specialized headsets to every employee. For quick inspections, customer-site troubleshooting, equipment identification, or occasional expert assistance, familiar mobile devices can be sufficient. The important element is not the device. It is the shared visual context.

MIXED REALITY AND HANDS-FREE SUPPORT
Mixed reality becomes particularly interesting when employees need both hands available. Imagine a technician working inside a machine while holding tools. Repeatedly putting down the tools to pick up a smartphone interrupts the process. With an appropriate mixed reality headset, the worker can continue looking at the equipment while the remote expert sees the worker's perspective. The technician's hands remain available for the task. Guidance can remain connected to the physical work environment. This makes hands-free remote assistance potentially useful for complicated maintenance, manufacturing, inspection, and service processes.

MICROSOFT TEAMS AND REMOTE ASSIST
Microsoft Teams plays an important role in the Remote Assist experience. Teams provides familiar communication capabilities including calls, meetings, chat, and contacts. Remote Assist uses that communication foundation while focusing the interaction on frontline work. A technician can connect with an expert already working within the organization's Microsoft environment. Another specialist can potentially join when additional expertise becomes necessary. The organization does not necessarily need to build a completely separate communication network specifically for remote support. The people employees already collaborate with through Teams can become part of the support process.

REMOTE ASSIST VS A NORMAL TEAMS CALL
At first glance, Remote Assist may sound like a Microsoft Teams video call. There is an important difference. A traditional Teams meeting primarily connects people. Remote Assist focuses that connection on the physical work environment. The remote expert is not simply watching another person's face through a webcam. They are looking at the machine, equipment, installation, component, or physical environment the frontline worker is trying to understand. Visual guidance can then help both people focus on the same physical object. That makes the conversation considerably more useful for hands-on technical work.

VISUAL ANNOTATIONS
One of the most useful concepts behind Remote Assist is visual annotation. Imagine an electrical cabinet containing several rows of nearly identical connectors. The remote expert says: "Check the connector beside the blue cable." There may still be several possible components. Instead, the expert can visually indicate the relevant area. They might circle a connector, place an arrow near a switch, or mark another part of the scene. The technician can then see exactly which area the expert is discussing. A small visual mark can eliminate several minutes of verbal explanation. This becomes particularly valuable when machinery contains many visually similar components

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

When a customer sends a chat message, email, phone request, or support case, they usually expect one thing: the right person should help them as quickly as possible. But customer service becomes complicated as organizations grow. A shared inbox that worked perfectly for five agents can quickly turn into a bottleneck when hundreds of requests arrive through multiple channels, in different languages, with different priorities, and requiring different technical skills. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Unified Routing in plain English. We explore how Unified Routing classifies incoming customer requests, determines priority, identifies required skills, considers agent availability and workload, and then routes the work to the most appropriate person. We also explain workstreams, queues, skills, capacity profiles, presence, push assignment, pick assignment, machine learning, fallback queues, and Copilot Service workspace.

WHAT IS DYNAMICS 365 UNIFIED ROUTING?
Dynamics 365 Unified Routing is an intelligent routing capability designed to automatically distribute incoming customer service work to appropriate agents. Think of it as a smart front desk. Imagine a large office building where visitors arrive with completely different needs. One person needs accounting. Another needs technical support. Another speaks Spanish and needs someone who can communicate with them. Another has an urgent appointment. A good receptionist does not simply point everybody toward the same waiting room. They understand what each visitor needs and direct them toward the right person. Unified Routing performs a similar function for customer service requests. Instead of simply asking "Which agent is next?", the system can consider what the customer needs, who has the necessary skills, who is available, how much work each agent already has, and how urgently the request should be handled. 

WHY BASIC CUSTOMER SERVICE QUEUES STOP WORKING
Imagine a small customer service department with five employees. Customers send emails to one shared support address. Every email enters the same queue. When an agent finishes their current task, they take the next request. For a small organization with one product, one language, and relatively few requests, this can work perfectly well. Then the organization grows. Customers begin contacting support through email, live chat, voice, messaging, web forms, and case records. Some customers have billing questions. Others need technical assistance. Some require support in another language. Some have routine questions. Others have critical problems affecting their business. Suddenly, the shared queue looks less like an organized support process and more like a pile of papers sitting on somebody's desk.

THE PROBLEM WITH FIRST-COME, FIRST-SERVED ROUTING
Traditional queues frequently focus on when a request arrived. But arrival time is only one factor. Imagine an experienced technical specialist spending an hour answering basic password questions. Meanwhile, a customer with a serious technical problem waits because nobody noticed that their case requires specialist knowledge. Eventually, another agent opens the case, realizes they cannot solve it, and transfers it. The customer waits again. The organization creates additional work. The specialist eventually receives the request anyway. Unified Routing attempts to reduce these unnecessary handoffs by considering the requirements of the request before assigning it. The goal is to get closer to: Right customer request → right team → right agent → right time.

BASIC ROUTING VS UNIFIED ROUTING
Basic routing can already provide useful structure. An organization might create a simple rule: Billing cases go to the billing queue. Technical cases go to the support queue. For straightforward customer service environments, that may be sufficient. But a queue answers only part of the routing question. It tells the system where the request should wait. It does not necessarily determine which person inside that queue has the appropriate expertise, who is currently available, who already has several active conversations, or whether another request should receive higher priority. Unified Routing addresses this larger assignment problem.

ONE ROUTING APPROACH ACROSS CUSTOMER SERVICE CHANNELS
One of the important ideas behind Unified Routing is applying a common routing approach across different types of customer work. A live chat and an email are obviously different interactions. A telephone call has different timing requirements from a case created through a web form. But they share the same fundamental routing problem: Who should handle this request? Unified Routing can evaluate incoming work according to the organization's configured rules and requirements. The channel becomes one part of the decision rather than requiring an entirely disconnected routing philosophy for every customer interaction.

SKILLS-BASED ROUTING
Skills are one of the most important concepts in Unified Routing. A skill represents something an agent knows how to handle. That might be: A language. A particular product. A technical area. A customer service specialization. A business function. A support level. Incoming work can also receive required skills. Dynamics 365 can then match the requirements of the customer request with the skills associated with available agents. 

A SIMPLE SKILLS-BASED ROUTING EXAMPLE
Imagine two agents. Maria understands the company's advanced product line and speaks Spanish. David specializes in account questions and currently has capacity for another email. A Spanish-language request about an advanced technical problem should not automatically go to David simply because he happens to be the next available person. The work requires Spanish and advanced product knowledge. Maria is therefore a much stronger match when she is available and has sufficient capacity. This illustrates the fundamental difference between basic distribution and intelligent routing. Availability alone does not necessarily make somebody the right agent.

THE TWO DECISIONS BEHIND UNIFIED ROUTING
Unified Routing essentially performs two connected operations. First, it determines what the incoming request needs. Then it determines who should receive it. Microsoft's routing process can therefore be understood as: Classification → Assignment Classification adds useful information to the work item. Assignment compares those requirements with available agents. Keeping these two stages separate makes the overall routing process easier to understand.

WHAT IS CLASSIFICATION?
Imagine an email entering Dynamics 365. Initially, it may contain a customer name, subject line, message, and other basic information. That alone may not tell the routing system enough. Is this a billing problem? A product failure? An account question? Which language does the customer require? Does the customer have premium support? Does the case require specialist knowledge? How urgent is the problem? Classification adds the information required to answer those questions. It turns a relatively vague customer request into structured work that the routing system can understand. 

CLASSIFICATION RULES
Organizations can configure rules that examine information associated with incoming work. For example, a rule might determine that a customer has a premium support agreement and therefore assign a higher priority. Another rule could inspect the case category and require a billing skill. Another could identify the customer's language and add that language as a routing requirement. The important point is that these decisions become repeatable. Instead of every agent manually deciding how a request should be categorized, the routing configuration applies the organization's service rules consistently.

MACHINE LEARNING AND ROUTING
Rules work particularly well when customer information is structured and predictable. But customers do not always describe the same problem using the same words. One customer might say: "My device won't start." Another writes: "The screen stays black." Another says: "I can't turn it on." These sentences may describe the same underlying problem. Creating manual rules for every possible variation quickly becomes difficult. The supplied episode explains that machine-learning-based capabilities can help predict the skills required for a request by examining patterns in customer text. Instead of creating a separate rule for every phrase, a model can help determine whether a request appears to require product expertise, billing knowledge, or another support skill. 

YOU DO NOT ALWAYS NEED MACHINE LEARNING
More intelligence does not automatically mean better routing. A small customer service team with clear case categories may be perfectly successful using straightforward rules. Machine learning becomes more relevant when volumes increase, customer descriptions vary significantly, and maintaining manual routing rules becomes increasingly difficult. The routing architecture should match the complexity of the actual service operation. Organizations should not create an AI problem where a simple business rule already solves the requirement. 

PRIORITY IS DIFFERENT FROM SKILLS Skills and priority answer two different questions. Skills ask: Who can solve this? Priority asks: How quickly should we deal with it? A routine request may safely wait behind a serious service disruption. A customer with a premium support agreement may require a faster response. An urgent operational problem may need to move ahead of several normal requests even when those requests arrived earlier. Unified Routing can use classification information to establish priority before an agent receives the work.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Imagine standing beside a large industrial machine and seeing the next repair instruction appear directly beside the panel you need to open. Instead of putting down your tools, walking back to a laptop, searching through a PDF, or trying to remember what an experienced technician told you during training, the information appears directly inside your field of view. That was the central idea behind Microsoft Dynamics 365 Guides. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Dynamics 365 Guides in plain English: what the mixed reality application was designed to solve, how Microsoft HoloLens brought instructions into the physical workplace, how companies could capture expert knowledge, how Microsoft Teams enabled remote assistance, and how Dynamics 365, Dataverse, Power Platform, Power BI, and AI could extend the experience. There is also an important strategic issue organizations need to understand: Microsoft has set December 31, 2026 as the end-of-availability date for Dynamics 365 Guides and Dynamics 365 Remote Assist. For organizations still using the technology, preserving the knowledge contained inside their Guides is therefore becoming just as important as understanding the technology itself.

WHAT IS DYNAMICS 365 GUIDES?
Dynamics 365 Guides is a Microsoft mixed reality application designed to bring step-by-step work instructions directly into the physical environment where employees perform a task. Instead of requiring a technician to repeatedly move between a machine and a manual, Guides could display digital instruction cards, images, videos, and 3D objects through a Microsoft HoloLens headset. The employee could still see the real machine, tools, equipment, coworkers, and surrounding environment. Digital information appeared alongside that physical world. This made Guides particularly interesting for scenarios involving manufacturing, maintenance, inspections, field service, training, assembly, and other repeatable physical processes. The fundamental concept was simple: Bring the instruction to the work instead of forcing the worker to leave the work to find the instruction.

THE PROBLEM: INSTRUCTIONS ARE OFTEN FAR FROM THE WORK
Physical work frequently happens far away from the information required to perform it. A technician may be servicing a pump. An operator may be assembling equipment. A maintenance employee may need to inspect dozens of components in a particular sequence. A quality inspector may need to compare a finished component against an approved standard. Traditionally, those employees might rely on paper manuals, PDFs, laptops, classroom training, or experienced colleagues. All of those methods can work. But they create a separation between where the knowledge lives and where the work happens. A technician reads the manual, returns to the machine, remembers as much as possible, completes part of the task, and then potentially returns to the documentation. That constant context switching creates friction.

WHY TRADITIONAL MANUALS CAN BECOME A PROBLEM
Imagine a new technician standing beside a machine they have never repaired. The manual refers to components by technical names and part numbers. The actual machine contains cables, covers, grease, connectors, labels, bolts, and dozens of components that look similar. The technician reads the manual. Then they look at the machine. Then they return to the diagram. Then they try to determine whether the component shown on the page is actually the component in front of them. An experienced technician may perform the same task almost automatically because years of experience have created practical knowledge that the manual does not fully communicate. Dynamics 365 Guides attempted to reduce that gap by putting visual guidance directly beside the physical object.

CAPTURING EXPERT KNOWLEDGE
Experienced employees often possess enormous amounts of undocumented knowledge. They know which cover should come off first. They know which tool fits into a difficult space. They recognize what a correctly installed component should look like. They know where common faults occur. They know which warning signs inexperienced employees frequently overlook. The problem is that much of this information exists primarily inside people's memories. When those employees are busy, working at another location, changing jobs, or retiring, organizations can lose valuable operational knowledge. Dynamics 365 Guides provided a way to convert some of that experience into structured digital instructions. An experienced technician, process engineer, or trainer could create a repeatable sequence that another employee could follow while standing directly beside the equipment. 

WHAT IS MIXED REALITY?
Mixed reality combines the physical environment with digital information. With Dynamics 365 Guides, an employee could wear a Microsoft HoloLens headset while continuing to see the real world. Digital elements could then appear within that environment. Those elements might include instructions, arrows, photographs, videos, or 3D models. This differs from a completely immersive virtual reality experience. The employee is not transported into a simulated factory. They remain inside the real factory looking at the real machine. The digital information appears alongside it. Think of a traditional manual as a document stored in another room. Mixed reality turns parts of that manual into signs positioned directly beside the equipment.

HOLOLENS AND HANDS-FREE WORK
One of the practical advantages of HoloLens was the ability to keep the worker's hands available. Physical jobs frequently require both hands. A technician may be holding a tool. An operator may need to stabilize a component. Someone may be wearing protective equipment. Trying to operate a smartphone or balance a laptop while performing that work can interrupt the process. With HoloLens, the headset becomes the display. The employee can continue looking at the equipment while digital information remains visible. This sounds like a relatively small change, but it can significantly alter the workflow for tasks where repeatedly stopping to check documentation creates delays.

TEXT, PHOTOS, VIDEO AND 3D OBJECTS
A Dynamics 365 Guide could combine several forms of instructional content. Text could explain what action the employee should perform. A photograph could show what the correctly completed step should look like. A short video could demonstrate a movement that would be difficult to describe clearly in several paragraphs. A 3D model could help the employee identify the component they need to inspect. The important difference was spatial placement. The content was not simply another video playing somewhere inside the headset. Authors could position digital elements inside the physical workspace. An arrow could appear near a particular panel. A 3D model could appear beside the component it represents. The employee could therefore connect the instruction with the real object more directly.

WHY SPATIAL PLACEMENT MATTERR
Consider the instruction: "Inspect the filter housing." That sentence may be perfectly clear to an experienced technician. A new employee may have no idea which of several similar components is the filter housing. A photograph can help. A 3D model can help further. But mixed reality can go another step by placing the guidance near the actual component. The employee does not need to mentally translate a two-dimensional diagram into the complicated physical machine standing in front of them. That reduction in interpretation is one of the most interesting aspects of mixed reality instructions.

CREATING A DYNAMICS 365 GUIDE
Guides did not automatically understand how a company's equipment worked. Someone needed to create the instructions. The process typically started with a subject matter expert such as an experienced technician, process engineer, or trainer. Using the Dynamics 365 Guides PC application, the author could create a sequence of steps. Each step could contain concise instructions and supporting media. The author could then use HoloLens inside the actual work environment to position relevant digital elements around the equipment. This combined two types of knowledge: Process knowledge — what needs to happen. Spatial knowledge — where it needs to happen. Together, those elements created the mixed reality guide.

GOOD GUIDES REQUIRE GOOD INSTRUCTIONS
Mixed reality does not automatically make bad documentation useful. If an instruction is unclear, putting it inside a headset does not solve the problem. If an arrow points vaguely toward several similar components, the employee still does not know which component matters. If a hologram blocks the worker's view of the equipment, the technology may create another problem. Good Guides therefore required concise wording, careful spatial placement, appropriate media, and genuine understanding of the physical workspace. Instructions needed to reflect how people actually performed the work rather than how someone sitting at a desk imagined the process worked.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

How many sales opportunities disappear because somebody intended to follow up but lost the email, missed the task, or simply forgot? Modern sales teams rarely suffer from a lack of customer data. They have CRM records, emails, meetings, notes, opportunities, tasks, forecasts, and relationship information. The bigger problem is understanding which information matters right now and what the seller should do next. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Sales Insights in plain English and explores how Microsoft uses AI, activity signals, relationship data, predictive scoring, conversation intelligence, and forecasting to help sales teams focus their attention. We look at the Sales Insights assistant, Auto Capture, Email Engagement, predictive lead and opportunity scoring, Sales Accelerator, relationship intelligence, Who Knows Whom, Talking Points, Conversation Intelligence, notes analysis, forecasting, Microsoft 365 integration, Microsoft Teams, and LinkedIn Sales Navigator. ㅤ

WHAT IS DYNAMICS 365 SALES INSIGHTS?
Dynamics 365 Sales Insights is a collection of AI-powered and intelligence capabilities designed to make the information inside Dynamics 365 Sales more actionable. Dynamics 365 Sales remains the CRM foundation. It contains accounts, contacts, leads, opportunities, activities, customer information, pipeline records, and sales history. Sales Insights sits on top of this information and looks for useful signals. An important activity might be overdue. A lead might resemble previous leads that successfully converted. Communication with an important account might have declined. An opportunity may show patterns associated with previous successful deals. Instead of expecting sellers to manually search thousands of records for these signals, Sales Insights can bring relevant information closer to their daily work. The objective is not more data. The objective is better guidance from the data the sales organization already has. 

WHY SALES TEAMS NEED INSIGHTS, NOT JUST MORE DATA
Imagine the traditional sales process. A salesperson keeps one spreadsheet containing prospects, searches Outlook for the latest customer email, writes notes after telephone calls, creates calendar reminders, and tries to remember which customer requested pricing last week. Then the sales manager asks: Which opportunities are likely to close this month? The answer can quickly become dependent on memory and intuition. The salesperson is not necessarily doing anything wrong. Sales simply generates enormous amounts of information. Every call creates notes. Every email creates another conversation. Every meeting creates potential follow-up actions. Opportunities move through stages. New people enter buying groups. Customer requirements change. Dynamics 365 Sales gives this information a structured home. Sales Insights attempts to turn that growing information into useful signals.

THE SALES INSIGHTS ASSISTANT
One of the everyday capabilities discussed in the episode is the Sales Insights Assistant. The assistant uses cards inside Dynamics 365 Sales to surface work that may require attention. That could include overdue tasks, upcoming meetings, or suggested next actions. Think of it like an inbox tray sitting on a salesperson's desk. Important items can rise closer to the top without making everything else disappear. Suppose you promised to send pricing information after Tuesday's customer call. Wednesday becomes unexpectedly busy. Two new leads arrive. A meeting runs longer than expected. Another customer calls. The promised pricing email never gets sent. An assistant card can bring that overdue follow-up back into view. That simple reminder can matter because customers rarely contact a salesperson to explain that the salesperson followed up too slowly. They may simply begin talking to somebody else.

ASSISTANT CARDS AND NEXT ACTIONS
Assistant cards should not be confused with automated sales decisions. The system can identify something potentially important. The salesperson still determines whether and how to act. An overdue task may still be relevant. Another task may no longer make sense because the customer situation changed. An upcoming meeting may require preparation. Another customer may suddenly require immediate attention. Sales Insights provides the signal. The salesperson provides the context and judgment. This distinction runs throughout the entire Sales Insights experience. The technology is designed to support the seller rather than replace the seller. 

AUTO CAPTURE
One of the biggest problems with CRM systems is keeping activity information current. Salespeople spend significant amounts of time inside email and meetings rather than filling out CRM forms. If every useful customer interaction needs to be manually copied into Dynamics 365 Sales, information inevitably gets missed. Auto Capture helps identify emails and meetings that appear related to customers already inside Dynamics 365 Sales. Those interactions can then be brought to the salesperson's attention for review. The important point is that finding an interaction does not necessarily mean every email should automatically become a permanent CRM record. Sales information still needs appropriate review. A private message, unrelated conversation, or incorrectly associated email should not become part of a customer history simply because software detected a possible relationship.

PREMIUM AUTO CAPTURE
The episode also discusses additional Auto Capture capabilities. Imagine a customer replies to an email and includes a colleague the salesperson has never previously met. That person may be part of the customer's buying group but does not yet exist inside Dynamics 365 Sales. Premium Auto Capture can help identify this situation and suggest creating a contact. The salesperson can then review the person's name, role, and context before deciding whether they actually belong inside the CRM. This illustrates an important principle: Automation can reduce data entry without eliminating data quality controls. The system helps prepare the work. The seller still confirms whether the information belongs in the customer record.

EMAIL ENGAGEMENT
Email Engagement provides sellers with additional information about tracked sales emails. Depending on the configuration, sellers can see signals such as whether a recipient opened an email or clicked a link. These signals need careful interpretation. An email open does not mean a customer intends to purchase. A customer not opening an email does not automatically mean they have no interest. But engagement information can provide useful context around timing. Imagine sending a proposal Monday morning. The prospect opens the message and clicks through to the pricing information but does not reply. Instead of simply sending exactly the same follow-up several days later, the salesperson now has another signal suggesting that a conversation might be useful. The signal provides context. The salesperson still needs to decide what an appropriate interaction looks like.

PREDICTIVE LEAD SCORING
Salespeople can only make a limited number of calls and conduct a limited number of meetings each day. When hundreds of leads exist inside the CRM, the obvious question becomes: Where should I start? Predictive lead scoring attempts to help answer that question. The system looks at patterns from previous sales information and compares those patterns with current leads. Depending on the organization's data, those patterns might involve lead sources, company information, job roles, activities, or other fields used during the sales process. The underlying question is relatively simple: When leads with similar characteristics appeared previously, how often did they move forward? The resulting score can help sellers prioritize a crowded lead list. ㅤ

PREDICTIVE SCORES ARE SIGNALS, NOT GUARANTEES
Suppose 200 leads arrive after an industry event. Without scoring, the salesperson might work through those leads alphabetically, according to registration time, or simply according to personal instinct. Predictive scoring can provide another method of prioritization. Leads resembling previous successful customers may receive greater attention earlier. That does not mean lower-scoring leads should be ignored. A new market may behave differently from historical customers. A promising prospect might have incomplete information. A new product could attract buyers unlike those in the historical training data. The score should therefore be treated as a priority signal rather than a final sales decision. ㅤ 

PREDICTIVE OPPORTUNITY SCORING
Predictive opportunity scoring applies a similar concept to deals already moving through the sales pipeline. An opportunity can contain information such as estimated revenue, expected closing dates, customer contacts, sales activities, and sales stages. Sales Insights can compare the active opportunity with patterns from previous sales outcomes. The result can provide an indication of how strongly the current opportunity resembles previous successful deals. Sellers can also look at how the score changes. A rising score may correspond with increased engagement or positive progress. A falling score can provide a reason to investigate what changed. Again, the score does not know whether the customer's budget has actually been approved or whether a competitor has suddenly changed the situation. It provides another piece of evidence.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Salespeople rarely struggle because they do not have enough tasks. The real challenge is deciding which customer deserves attention next, what action should happen, and what context is needed before reaching out. Emails arrive in Outlook. Meetings fill the calendar. Customer information lives inside CRM records. Leads respond to marketing activities. Colleagues leave notes. Opportunities change. Follow-up reminders compete with urgent customer requests. The result can be a busy sales day that still misses the most important opportunities. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Sales Accelerator in plain English and explores how its guided selling capabilities help sales teams prioritize leads and opportunities, organize daily activities, create repeatable sales sequences, and keep customer context close to every interaction. We look at Up Next, the Sales Accelerator work list, sequences, predictive scoring, customer engagement, sales insights, Copilot, Microsoft Teams, Outlook integration, and guided selling—and explain where automation helps and where human judgment remains essential.

WHAT IS DYNAMICS 365 SALES ACCELERATOR?
Dynamics 365 Sales Accelerator is a guided selling experience inside Dynamics 365 Sales. It does not replace Dynamics 365 Sales. Dynamics 365 Sales remains the larger CRM environment where organizations maintain accounts, contacts, leads, opportunities, activities, pipeline information, and sales history. Sales Accelerator provides a more focused working experience on top of that information. Think of it as the seller's daily desk. Instead of opening Dynamics 365 and looking through thousands of CRM records, Sales Accelerator helps answer a much more practical question: Who should I work with today, and what should I do next? It brings together leads, opportunities, activities, suggested actions, and customer context so sellers have a clearer starting point for their day.

WHY SALES WORK BECOMES FRAGMENTED
Consider a typical sales morning. You open Outlook and find customer emails, internal conversations, newsletters, meeting invitations, and a response from someone who requested a proposal last week. Your calendar says you have another call in 30 minutes. Your phone shows a missed call. A spreadsheet contains leads that never reached the CRM. Dynamics 365 contains another list of opportunities. Meanwhile, a colleague asks about a customer and your sales manager wants an updated forecast. None of these activities is particularly difficult individually. The difficulty comes from determining what deserves attention first. Traditional approaches rely heavily on personal memory, Outlook flags, calendar reminders, CRM tasks, spreadsheets, and sometimes sticky notes. When the day becomes busy, the next important customer action can disappear inside all that activity. ㅤ

BUSY SALES TEAMS ARE NOT ALWAYS PRODUCTIVE SALES TEAMS
A salesperson can spend an entire morning sending emails, updating CRM records, attending meetings, completing tasks, and still spend too little time with customers who are actually ready to move forward. This is one of the fundamental problems Sales Accelerator tries to address. Imagine two prospects. One has recently replied to an email, visited pricing information, and asked another question. The other has not responded for several weeks. If both appear inside the same unfiltered task list, the salesperson may simply work from top to bottom. That does not necessarily represent the real business priority. Sales Accelerator attempts to bring activity, timing, sales information, and planned actions together so sellers can make better prioritization decisions.

THE THREE CORE PARTS OF SALES ACCELERATOR
The episode focuses on three important components of Dynamics 365 Sales Accelerator: Up Next and the work list help sellers determine which leads and opportunities require attention. Sequences create repeatable follow-up processes around leads and opportunities. Customer context gives sellers the background they need before making the next call or sending the next message. These components work together. The work list identifies a customer requiring attention. The sequence suggests the next planned activity. The CRM record provides the history and context required to perform that activity appropriately. That combination turns Dynamics 365 from a large collection of customer records into a more practical daily selling workspace.

WHAT IS THE SALES ACCELERATOR WORK LIST?
The Sales Accelerator work list provides sellers with a focused collection of leads and opportunities requiring attention. Instead of looking at every record inside the CRM, sellers see active sales work relevant to their day. Each item can point toward an appropriate activity such as making a call, sending an email, or completing another follow-up action. The difference sounds simple, but it can significantly change how sellers begin their working day. Instead of asking: "Where should I start?" the seller has a guided list of potential priorities. The underlying customer information remains available so the seller can review context before taking action.

UP NEXT IN DYNAMICS 365 SALES
Up Next focuses attention on the next activities associated with leads and opportunities. The objective is not simply to produce another task list. Up Next connects the task with the customer record and the surrounding sales information. A task saying "Call Priya" provides very little useful context by itself. But that task becomes considerably more useful when the seller can also see that Priya attended a meeting, responded to a previous email, asked about pricing, or is connected with an active opportunity. The seller can then begin the conversation from the customer's actual situation rather than treating every interaction like a cold first contact. 

PRIORITIZING LEADS AND OPPORTUNITIES
The work list can consider several signals when determining which records deserve attention. The episode discusses areas including predictive scoring, organizational rules, recent customer activity, overdue work, and planned sequence activities. For example, an organization might decide that a new website lead should receive attention within a defined number of hours. An opportunity approaching its expected closing date might require review. A customer response might deserve immediate attention even if the originally scheduled follow-up was planned for later. These signals allow organizations to turn successful sales habits into processes the system can help surface consistently.

PREDICTIVE LEAD SCORING
Predictive scoring helps sellers identify leads that may have a higher probability of progressing based on patterns within available sales information. The important word is signal. A predictive score is not a guarantee. If one lead recently opened an email, followed a link, and scheduled a conversation while another has remained inactive for weeks, the first lead may appear more promising. That does not mean the system knows with certainty who will purchase. It means the available information suggests that one record currently deserves closer attention. Salespeople still need to apply business knowledge and relationship context when determining actual priorities. ㅤ

OVERDUE SALES ACTIVITIES
Sales Accelerator can also keep overdue activities visible. An overdue call should not simply disappear because several newer activities arrived. The salesperson can see that the activity requires attention and determine what to do. Perhaps the call still needs to happen. Perhaps it should be rescheduled. Perhaps the customer situation has changed and the original activity no longer makes sense. The important point is that the salesperson makes an explicit decision rather than relying entirely on memory to remember forgotten follow-ups.

SALES PRIORITIZATION STILL NEEDS HUMAN JUDGMENT
Sales Accelerator does not automatically understand every customer relationship. Imagine the work list identifies one opportunity as the highest priority. At the same time, a strategic customer calls with an urgent problem. The customer problem may obviously deserve immediate attention regardless of what the score says. Similarly, a salesperson may have personally promised a customer that they would call before lunch. The CRM algorithm may not fully understand the importance of that commitment. Sales Accelerator should therefore be viewed as guidance rather than an unquestionable command system. The seller remains responsible for deciding what actually happens next. 

WHAT ARE SALES SEQUENCES?
Knowing who to contact solves only part of the problem. The seller also needs to know what follow-up should happen. This is where sequences become important. A sequence is a planned series of sales activities connected to a lead or opportunity. Think of it as a sales follow-up blueprint. A sequence could contain an introductory email, followed by a telephone call, followed by a waiting period, another follow-up task, and then another email if the customer has not responded. The objective is to create a repeatable sales process without forcing every salesperson to manually recreate the same follow-up plan for every new lead.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

HR teams manage some of the most important and sensitive information inside an organization. Employee records, organizational structures, leave requests, benefits, compensation information, skills, certifications, training, performance, approvals, and onboarding tasks all need to remain accurate and accessible to the right people. The problem begins when that information is spread across spreadsheets, email conversations, shared folders, HR applications, manager-maintained lists, and disconnected systems. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Human Resources and how it creates a connected environment for core HR information and everyday people processes. We explore employee records, organizational structures, employee and manager self-service, leave and absence management, benefits, compensation, learning and development, HR workflows, onboarding, automation, reporting, Microsoft Teams, Power BI, and integrations with payroll and other HR systems.

WHAT IS DYNAMICS 365 HUMAN RESOURCES?
Microsoft Dynamics 365 Human Resources is a cloud-based HR solution designed to give organizations a central place for employee information and common HR processes. Think of it as the digital HR floor inside an organization. Employee records live in one controlled environment. Requests can follow predefined approval processes. Managers can access information about their teams. Employees can perform appropriate self-service activities. HR can manage policies and maintain the underlying people information. Instead of employees and managers carrying information between disconnected systems, the organization can create clearer HR processes around a shared employee record. The goal is not necessarily to put every people-related process into one application. Organizations may still use specialized solutions for payroll, recruitment, learning, or other functions. Dynamics 365 Human Resources provides the central people information and HR processes those connected systems can depend on.

THE PROBLEM OF FRAGMENTED HR DATA
Consider what happens when a new employee joins a company. HR enters the employee's information into one system. Their manager adds them to a separate team list. Payroll needs information in another application. Training materials are stored somewhere else. Benefits information arrives through email. Initially, everything may appear to work. But every additional copy of the employee record creates another opportunity for information to become outdated. The employee changes departments. Their manager changes. They move to another address. Their working hours change. They complete another certification. Suddenly, several systems contain different versions of the same person. Dynamics 365 Human Resources addresses this problem by providing a shared employee record around which HR processes can operate.

THE EMPLOYEE RECORD
At the center of Dynamics 365 Human Resources is the employee profile. This is considerably more than a digital contact card containing someone's name, telephone number, and job title. An employee profile can contain job information, contact details, work history, skills, certifications, interests, accomplishments, and training information. This creates a more complete professional record. Two employees may have exactly the same job title while possessing very different skills and experience. One project manager might hold a particular certification. Another may speak several languages. Another may have completed training required for a future role. Keeping this information connected to the employee record gives HR and managers a better foundation for staffing, development, training, and workforce decisions.

ORGANIZATIONAL STRUCTURES
Dynamics 365 Human Resources also helps organizations describe how their workforce is structured. The system can record departments, jobs, positions, managers, and reporting relationships. These concepts have different purposes. A department identifies where work takes place within the organization. A job describes a type of work. A position represents a particular place within the organization that can be filled by an employee. For example, an organization could employ many people with the job "Warehouse Associate," while every employee occupies a particular position connected with a specific department and reporting structure. Connecting these elements allows the organizational structure to become a working part of HR processes rather than a static organizational chart updated occasionally.

SKILLS AND CERTIFICATIONS
Employee skills and certifications are another important part of the employee profile. Imagine a manager asking HR: Who on my team currently holds the certification required for this project? Without structured HR information, answering that question might require searching spreadsheets, old training documents, emails, or individual employee records. Dynamics 365 Human Resources provides a more direct starting point by connecting skills and certifications with employee profiles. Certification dates can also matter. Some professional certifications or mandatory training requirements expire. Keeping those dates connected with employee information helps HR and managers identify when qualifications require attention. This becomes especially valuable in environments where particular jobs or projects require specific certifications.

SECURITY AND ROLE-BASED ACCESS 
HR systems contain sensitive information. That means not everyone should have access to everything. Employees may need access to their own information. Managers may require information about their teams. HR professionals may require broader access for legitimate HR responsibilities. Dynamics 365 Human Resources uses roles and permissions to control who can view or modify different areas. The source describes this like different doors inside a staff-only office. Not everyone receives the master key. Organizations need to determine which employees require access to particular information and configure security, privacy, and compliance controls accordingly. Technology provides the controls, but organizations remain responsible for establishing appropriate policies around employee data. 

EMPLOYEE SELF-SERVICE
A good HR platform should not require employees to email HR every time they need basic information. Employee self-service gives people a clearer way to handle routine HR activities themselves. Depending on the organization's configuration, employees can review their profiles, update permitted information, check leave details, complete assigned tasks, and submit HR requests. Instead of emailing: "How many vacation days do I have left?" the employee can check their available balance. Instead of wondering whether HR received a request, the employee can submit it through a defined process and follow its status. This can reduce repetitive administrative work for HR while giving employees more direct access to appropriate information.

MANAGER SELF-SERVICE
Managers need a different perspective. They need to understand who works within their team, reporting relationships, upcoming absences, employee information relevant to their responsibilities, and requests waiting for approval. Manager self-service gives managers access to appropriate information without requiring HR to manually answer every routine question. This can make common management processes significantly more efficient. The important point is that managers and HR are working from connected people information instead of maintaining separate team spreadsheets that gradually become inconsistent.

LEAVE AND ABSENCE MANAGEMENT
Leave management demonstrates how connected HR processes can improve a routine employee experience. Imagine an employee named Maya requesting three days of annual leave. The system can consider the employee's available balance and the company's configured leave rules. The request is routed to Maya's manager. The manager reviews the dates and approves or declines the request. Maya can see the result. The leave record reflects the decision. HR can review the request history. Instead of the approval existing only as an email saying "approved," the complete process becomes part of a structured HR workflow.

LEAVE POLICIES AND COMPANY RULES
Leave is more complicated than selecting several dates on a calendar. Organizations have policies covering working days, weekends, public holidays, leave categories, balances, eligibility, and other conditions. Dynamics 365 Human Resources can apply configured company rules when processing leave requests. For example, if a public holiday occurs during an employee's requested absence, the system can handle that date according to the organization's configured leave policy. This helps move policy enforcement away from manual interpretation for every routine request.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Most developers think of a database as the place where an application stores information. Tables, transactions, indexes, stored procedures, reporting, backups, and reliable data storage are the traditional responsibilities we associate with SQL. But what happens when the database itself becomes an active participant in the application architecture? In this episode of M365 FM, Mirko Peters talks with Dirceu Resende about how Azure SQL Database is evolving beyond traditional data storage. The conversation explores REST API integration, automation, external services, security, performance, Microsoft Fabric, Power BI, AI, vector search, RAG, observability, and the changing architectural role of databases inside modern applications. Dirceu brings a combination of database, business intelligence, Microsoft, and community experience to the discussion. His career spans database development and performance tuning, business intelligence, Power BI, and cloud technologies, including previous work at Microsoft as a Senior Program Manager for Power BI.

AZURE SQL DATABASE IS BECOMING MORE THAN A DATABASE
Azure SQL Database provides the familiar relational capabilities of SQL Server while removing much of the infrastructure management traditionally associated with running a production database. Organizations can use a managed cloud database without having to directly maintain the underlying operating system and infrastructure. Azure also provides capabilities around security, availability, backups, performance, and integration with other cloud services. But Dirceu argues that one of the most interesting developments is what Azure SQL can now do outside the traditional boundaries of the database. Azure SQL Database can make HTTP requests and communicate with external services. This creates scenarios where the database can participate directly in workflows that previously required another application or integration layer. The database is no longer necessarily waiting passively for an application to tell it what to do.

AZURE SQL DATABASE VS MANAGED INSTANCE VS SQL SERVER
Choosing the correct SQL deployment model still depends heavily on application architecture. Dirceu explains that Azure SQL Managed Instance provides an experience closer to traditional SQL Server. It supports scenarios involving multiple databases within an instance and capabilities that organizations migrating existing SQL Server workloads may require. Azure SQL Database is more naturally aligned with independent databases and architectures where applications or microservices have separate database resources. If an application depends heavily on cross-database queries, linked services, SQL CLR, or other traditional SQL Server capabilities, migration may require architectural changes rather than simply moving the existing database into Azure SQL Database unchanged. This makes workload assessment an important part of any SQL modernization strategy. 

WHY AZURE SQL FITS MODERN APPLICATION ARCHITECTURES
Moving data into Azure can make integration with other Azure and Microsoft services significantly easier. Applications running through services such as Azure App Service, containers, or Kubernetes can operate closer to the database. Microsoft Fabric and Power BI can also consume Azure SQL information through increasingly integrated architectures. Azure SQL Database additionally receives cloud capabilities that may arrive later in traditional SQL Server releases. Dirceu highlights sp_invoke_external_rest_endpoint as an important example because it allows Azure SQL Database to communicate directly with REST endpoints. That seemingly simple capability fundamentally changes what developers can consider doing inside or close to the database.

WHEN THE DATABASE BECOMES AN ACTIVE APPLICATION COMPONENT
Traditional application architecture often places the database behind an application layer. The application receives requests, executes business logic, communicates with other systems, and finally reads or writes information to the database. That separation remains useful and appropriate in many architectures. But Azure SQL can now perform more activities independently. Dirceu describes scenarios where the database can retrieve information from an external API, combine it with application data, work with information stored in Azure Blob Storage, and initiate other processes without requiring a separate application to orchestrate every individual step. This does not mean developers should move every application function into SQL. It means architects now have another option. 

CALLING REST APIS DIRECTLY FROM AZURE SQL
REST API integration is one of the central topics of this episode. If an external service provides an appropriate API, Azure SQL can potentially communicate with it. This opens the door to integrations with communication platforms, SaaS applications, Microsoft 365 services, AI platforms, monitoring systems, and custom applications. The database can therefore respond to business information rather than simply storing it. Imagine an order reaching the database. Instead of waiting for another application to periodically discover the new order, a database-driven process could potentially initiate an appropriate external action. This creates interesting opportunities for event-driven and data-driven architectures.

USING AI TO ANALYZE CUSTOMER FEEDBACK
One example discussed in the conversation involves customer feedback. Imagine an application that stores thousands of customer comments inside Azure SQL Database. Manually reading every comment and classifying whether the customer is satisfied, unhappy, extremely dissatisfied, or enthusiastic quickly becomes impractical. Azure SQL can potentially send that information to an AI or cognitive service through an API. The external service analyzes the text and returns a classification or score. That information can then be stored alongside the original customer feedback. The business could identify extremely dissatisfied customers requiring immediate attention or particularly satisfied customers relevant to another business process. The database becomes part of the AI workflow rather than simply the final storage destination. 

AI-POWERED DATA CLEANING
Another practical scenario involves data quality. Anyone who has worked with CSV files, spreadsheets, FTP integrations, or external data feeds knows how inconsistent incoming information can become. Locations can be misspelled. Values may use different formats. Names can contain unexpected variations. Hundreds of columns can require complex transformation rules. Historically, developers and data engineers might create substantial amounts of custom code to normalize this information. Dirceu discusses how AI services can potentially help classify, standardize, and clean incoming data. Instead of attempting to anticipate every possible incorrect value through manually created rules, the database can send problematic information to an AI service and use the result as part of the data preparation workflow. 

EMAIL, SMS, TEAMS, SLACK AND EXTERNAL SERVICES
REST APIs also make communication scenarios possible. Dirceu discusses integrations where Azure SQL could work with services capable of sending emails, SMS messages, WhatsApp messages, Telegram notifications, or Slack messages. A database could therefore participate in operational alerting. Imagine inventory falling below a defined threshold. A scheduled database process detects the condition and initiates a notification to the employee responsible for purchasing. The same principle could apply to failed processes, unusual business conditions, customer activity, or operational alerts. The important architectural change is that the trigger can originate directly from information already inside the database. 

MICROSOFT 365 AND THIRD-PARTY API INTEGRATION
The same concept extends beyond simple notifications. Dirceu discusses the potential to integrate with Microsoft 365 services and third-party platforms when appropriate APIs are available. A business event occurring inside the database could potentially create another action in a connected business application. For example, information could result in creating a task, updating another system, creating a lead, or initiating another business process. The exact possibilities depend on the capabilities and authentication mechanisms exposed by the target service. This turns REST API support into a general integration capability rather than a feature designed for one specific scenario. 

SYNCHRONOUS VS ASYNCHRONOUS DATABASE INTEGRATION
Not every business process should happen immediately. The episode distinguishes between synchronous and asynchronous integration patterns. A synchronous process could respond when information reaches the database. An order is inserted, a database process detects the event, and another action happens immediately. An asynchronous approach works differently. A scheduled process might periodically collect everything that happened during a defined period and then perform a batch action. For example, rather than sending ten individual notifications for ten orders, the system could generate one summary containing all ten orders. The right architecture depends on whether the business process requires immediate action or whether delayed and grouped processing is more appropriate. 

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

What happens when the same customer appears in three different systems—and every system tells a different story?Sales sees an open opportunity. Customer service sees recent complaints. Marketing sees email clicks and website activity. An order system knows the customer has already purchased twice. Each department has useful information, but nobody has the complete picture.In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Customer Insights - Data in plain English and explores how organizations can bring fragmented customer information together, unify records, create 360-degree customer profiles, calculate measures, build segments, use AI-powered predictions, and activate customer insights across Microsoft business applications.Dynamics 365 Customer Insights - Data is Microsoft's Customer Data Platform (CDP). Its purpose is not to replace CRM, sales, service, or marketing applications. Instead, it connects information from those systems to create a more complete and usable understanding of each customer.

WHY SCATTERED CUSTOMER DATA CREATES BAD DECISIONS
Most organizations already have significant amounts of customer data. The problem is that the information is often distributed across multiple systems.Dynamics 365 Sales may contain contacts, accounts, opportunities, calls, meetings, quotes, and notes. Customer service systems contain cases, complaints, product issues, and support conversations. Marketing systems track email opens, clicks, forms, event registrations, and website engagement. Order platforms contain purchases and returns.Every system provides a useful perspective, but none necessarily provides the complete customer story.This can create situations where sales approaches a customer who currently has a serious support problem, marketing sends an upgrade promotion to someone who just purchased the product, or customer service fails to recognize that the caller is one of the company's most important customers.The problem is not necessarily missing information. The information exists—it simply is not connected.

WHAT IS DYNAMICS 365 CUSTOMER INSIGHTS DATA?
Dynamics 365 Customer Insights - Data is a Customer Data Platform, commonly abbreviated as CDP.A CDP brings customer information from different approved sources together, identifies records that appear to represent the same customer, and creates unified customer profiles that other business processes can use.Think of it as a central customer records room.Sales contributes customer and opportunity information. Service contributes cases and interactions. E-commerce or order systems contribute purchases and returns. Websites contribute digital interactions. Other business applications contribute additional customer information.Customer Insights - Data organizes these records and attempts to connect the information belonging to the same customer.

WHAT IS A 360-DEGREE CUSTOMER VIEW?
The term 360-degree customer view sounds complicated, but the underlying concept is straightforward.Instead of understanding a customer from only one perspective, organizations can combine multiple types of information into a broader profile.That profile might show who the customer is, what they purchased, which service cases they opened, which events they attended, and how they recently interacted with the organization online.It is not a magical perfect view of everything about a customer.It is a more complete business view created from the customer information an organization has legitimately connected.

CUSTOMER DATA TYPES
Customer information can come in many forms.Demographic or profile information can include names, addresses, job titles, organizations, and contact information.Transactional data can contain purchases, payments, returns, subscriptions, or reservations.Behavioral information can describe actions such as visiting a webpage, opening an email, registering for an event, submitting a form, or using an application.Operational information can provide additional context from service processes, inventory systems, or connected devices.Combining these different types of data allows organizations to understand more than what appears in a single CRM record.

CUSTOMER INSIGHTS DATA VS CUSTOMER INSIGHTS JOURNEYS
Microsoft uses the Customer Insights name for two closely related areas, but their responsibilities are different.Customer Insights - Data brings customer information together, creates unified profiles, calculates insights, and builds customer segments.Customer Insights - Journeys focuses on customer communications and journeys across channels such as email and text messaging.An easy way to remember the distinction is:Data understands the customer. Journeys communicates with the customer.Customer Insights - Data can prepare the audience and customer context. Customer Insights - Journeys can then use that information when the organization decides how and when to communicate.

CUSTOMER INSIGHTS DATA VS DYNAMICS 365 SALES
Dynamics 365 Sales and Customer Insights - Data also perform different jobs.Dynamics 365 Sales gives sales professionals the tools required to manage leads, opportunities, accounts, activities, and customer relationships.Customer Insights - Data takes a broader perspective.It can incorporate information from Dynamics 365 Sales while also connecting approved information from service platforms, websites, order systems, cloud data platforms, and other sources.It therefore extends the customer context available around CRM processes rather than simply replacing Dynamics 365 Sales.

BUILDING THE UNIFIED CUSTOMER PROFILE
Creating a unified customer profile begins by bringing appropriate data sources into a Customer Insights environment.An environment acts as a controlled workspace where customer information can be imported, prepared, unified, and managed.Organizations then connect the sources containing relevant customer information.These sources may contain customer tables, order tables, service records, website interactions, or other structured business information.The challenge is that different systems rarely describe customers in exactly the same way.

DATAVERSE, FABRIC, AZURE AND OTHER DATA SOURCES
Organizations using Dynamics 365 and Power Platform may already have significant amounts of customer information stored in Microsoft Dataverse.Customer Insights - Data can also work with data from platforms discussed in the episode including Azure Data Lake, Microsoft Fabric OneLake, and Azure Synapse Analytics.Power Query connectors provide another method for bringing information from databases, business applications, and other connected sources into the customer data environment.The purpose is to connect relevant customer information regardless of whether every source uses the same structure.

DATA MAPPING
Different systems often use different names and formats for the same information.One database might use a field called "Email Address." Another might simply use "Email." Phone numbers might appear with or without country codes. Names can contain different formatting, titles, or spelling.Mapping tells Customer Insights what those incoming fields actually represent.Organizations identify fields representing information such as names, email addresses, phone numbers, customer IDs, addresses, and other attributes useful for identifying customers.Relationships between business records also need to be understood.An order means little in a unified profile unless the system can determine which customer placed it.

CUSTOMER MATCHING
Matching is one of the most important parts of customer data unification.Suppose Alex Morgan appears in Dynamics 365 Sales using a work email address, in a support platform using a personal email address, and in a webinar registration using a name and telephone number.Those records may represent the same person.However, matching customer information is not as simple as automatically joining identical names.Two different people can have the same name. Family members may share email addresses. Customers change jobs and email addresses. Phone number formats vary.Customer Insights - Data therefore allows organizations to define matching conditions based on appropriate combinations of identifying information.The objective is to connect records when there is sufficient evidence that they represent the same customer.

DUPLICATE REMOVAL
Before creating the wider customer profile, organizations also need to deal with duplicate records.A customer might appear twice because someone submitted a web form more than once, an import created another contact, or another business process accidentally created duplicate information.Duplicate removal helps prevent a single customer from being represented multiple times before broader unification takes place.Clean source data therefore remains important even when sophisticated customer data technology is available.

THE GOLDEN CUSTOMER RECORD
After matching and deduplication, Customer Insights - Data can create a unified customer profile.This is sometimes described as a golden record.The term does not mean that the platform creates a magically perfect version of the customer.Instead, it represents the best combined customer profile that can be created from the approved information and matching rules provided by the organization.A unified profile might combine contact information from one source, account relationships from another, purchase history from a commerce system, and service history from another application.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

A customer discovers a jacket online, checks whether it is available in a nearby store, orders it for pickup, and later returns it at another location. From the customer's perspective, this should be one simple shopping journey. Behind the scenes, however, that transaction can involve e-commerce, point of sale, inventory, customer information, pricing, fulfillment, payments, and returns.In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Commerce in plain English and explores how it connects physical stores, e-commerce, point of sale, products, inventory, pricing, customers, orders, loyalty, fulfillment, and retail operations.Rather than treating stores, websites, and back-office systems as separate environments, Dynamics 365 Commerce provides a connected foundation for modern omnichannel retail.

WHAT IS DYNAMICS 365 COMMERCE?
Dynamics 365 Commerce is Microsoft's platform for connecting the processes behind selling products across physical stores, websites, and other commerce channels.Retailers need consistent answers to basic questions: What products do we sell? What does each product cost? Where is inventory available? Which orders require action? What has a customer purchased previously?When different systems provide different answers, problems quickly appear. A website might display one price while the store displays another. A product might appear available online even though the physical inventory is unavailable. Store employees may be unable to access an order created through the website.Dynamics 365 Commerce connects these activities around shared business information.It is therefore much more than an e-commerce website builder or point-of-sale application.

FROM DYNAMICS 365 RETAIL TO DYNAMICS 365 COMMERCE
Dynamics 365 Commerce evolved from Dynamics 365 Retail, which primarily focused on physical retail operations and point of sale.Modern shopping journeys no longer remain within a single channel.Customers might discover a product online, inspect it in a physical store, order it through their phone, collect it somewhere else, and later contact customer service.Commerce is designed around this reality.The individual channels become different entrances into the same connected retail operation rather than isolated businesses with separate information.

OMNICHANNEL RETAIL
Omnichannel commerce means customers can move between channels while the underlying business information remains connected.A customer might begin a purchase on a smartphone and complete it inside a store. Another customer might purchase online and collect the order from a local branch.Someone else might purchase online but return the item to a completely different physical store.The customer should not need to understand which internal system originally processed the transaction.Dynamics 365 Commerce connects customer-facing channels with products, prices, inventory, customer records, orders, and fulfillment information so retailers can create more consistent experiences across those channels.

REAL-TIME INVENTORY VISIBILITY
Inventory visibility is fundamental to omnichannel retail.If a website tells a customer that a product is available for collection, the business needs sufficient inventory information to support that promise.A product existing in the catalog does not necessarily mean it is physically available in the customer's preferred location.Dynamics 365 Commerce connects online shopping experiences with inventory information from stores and warehouses, allowing retailers to provide customers with more realistic availability information.This enables experiences such as checking local availability before visiting a store.

BUY ONLINE, PICK UP IN STORE
Buy Online, Pick Up In Store scenarios connect digital shopping with physical retail locations.A customer can find a product online, place the order, and select a nearby store as the collection point.Behind that simple customer choice, the retailer needs to know whether the selected location has appropriate inventory, whether the store can prepare the order, and when the product will realistically be ready.The store effectively becomes part of the e-commerce fulfillment network.This is one example of how Dynamics 365 Commerce turns physical retail locations into more than traditional sales floors.

SHIP FROM STORE
Stores can also become fulfillment locations.If a customer places an online order and a particular store has the required inventory, the retailer may choose to fulfill the order from that store rather than a central warehouse.This can potentially improve inventory utilization and give businesses additional options for fulfilling customer demand.The customer simply sees that the product can be delivered.Behind the scenes, Commerce helps connect the order with the location responsible for preparing it.

CROSS-CHANNEL RETURNS
Returns demonstrate why connected commerce information matters.Imagine a customer purchases an item online but later decides to return it at a physical store.In a disconnected environment, the employee might be unable to access the original online order and could tell the customer that online purchases must be handled through another system.With connected order and customer information, store employees can locate the relevant transaction and process supported return scenarios without treating the website and physical store as completely separate businesses.That creates a much more consistent customer experience.

ENDLESS AISLE
A physical store has limited shelf space. The retailer's wider inventory network does not necessarily have the same limitation.The endless aisle concept allows store employees to look beyond inventory physically available in their current location.If a customer wants a particular shoe size that has sold out locally, an employee may be able to check inventory elsewhere, place the order, and arrange delivery or pickup from another location.The physical shelf therefore stops defining the complete product selection available to the customer.

DISTRIBUTED ORDER MANAGEMENT
When several stores and warehouses can fulfill the same order, the retailer needs to determine which location should actually handle it.This is where Distributed Order Management becomes important.Dynamics 365 Commerce can use retailer-defined business rules to determine an appropriate fulfillment location based on factors such as available inventory, delivery commitments, and locations capable of fulfilling the order.Instead of every order entering a queue where employees manually determine the fulfillment location, the platform can help route orders according to established business rules.People still perform the physical work of picking, packing, shipping, and handing products to customers.

STORE COMMERCE AND POINT OF SALE
Physical store employees need fast access to information while customers are standing in front of them.The Store Commerce app provides point-of-sale capabilities for retail employees.Cashiers can use it at traditional checkout counters, while sales associates can use supported mobile devices around the store.According to the episode, Store Commerce supports environments including Windows, iOS, Android, and macOS, giving retailers flexibility in how employees interact with the platform.The point of sale becomes more than a payment terminal. It becomes an operational tool for helping customers.

WHAT STORE EMPLOYEES CAN DO
Store Commerce supports activities around the complete in-store customer interaction.Employees can process sales, find customers, check inventory, work with orders, handle returns, and access reporting.The platform can also support operational activities such as shifts and cash management.Different employees have different responsibilities, so role-based experiences can provide functionality appropriate to cashiers, managers, sales employees, or stock workers.The objective is to give employees access to the information required for their role without forcing them to navigate multiple disconnected applications.

CONSISTENT PRICING AND BUSINESS RULES
Customers expect prices and promotions to remain consistent across channels according to the retailer's policies.Commerce provides a shared foundation for product information, pricing, promotions, customer information, and order processing.Store employees might interact with this foundation through Store Commerce while online customers use the e-commerce storefront.Although the interfaces are different, they can rely on the same underlying commerce rules.This helps retailers reduce situations where customers encounter completely different information depending on which channel they use.

WHAT IS THE COMMERCE SCALE UNIT?
One of the important technical components explained in the episode is the Commerce Scale Unit.Think of it as an engine behind the customer-facing commerce experiences.A shopper might interact with a website. Another customer might use a mobile application. A store employee might use Store Commerce.Behind these different interfaces, the Commerce Scale Unit processes requests and applies commerce rules.Customers never need to know that this engine exists. They simply expect the correct product information, pricing, availability, promotions, and order actions.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Customer projects can become complicated quickly. Sales has the customer relationship and quote. Project managers have schedules and tasks. Resource managers need to know who is available. Consultants record hours and expenses. Finance needs to understand costs, revenue, and what can actually be invoiced.In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Project Operations and how Microsoft connects project sales, project management, resource planning, time tracking, expenses, billing, and financial processes within one project-focused platform.The episode follows the complete lifecycle of a customer project—from the first sales conversation and project quote through planning, staffing, delivery, time and expense management, financial tracking, and finally customer invoicing.

WHAT IS DYNAMICS 365 PROJECT OPERATIONS?
Microsoft Dynamics 365 Project Operations is designed for organizations that sell project-based services. These businesses are not simply selling products. They are selling expertise, professional services, consulting hours, engineering work, implementation projects, design services, development work, or other customer engagements where people, time, costs, contracts, and billing need to remain connected.Without a connected system, different departments often create their own version of a project. Sales knows what was promised. Delivery creates another project plan. Employees record hours somewhere else. Finance receives approved hours and expenses later and then tries to determine what should appear on the customer's invoice.Dynamics 365 Project Operations connects these areas around shared project information.The objective is not to make every department use exactly the same interface. Salespeople, consultants, project managers, resource managers, and finance professionals have different responsibilities. What matters is that the underlying project information remains connected.

FROM SALES OPPORTUNITY TO PROJECT DELIVERY
A customer project begins before the first task is created.During the sales process, someone needs to determine what the customer actually needs, which roles will be required, how many hours may be necessary, when work could start, what the project should cost, and how the customer will be charged.Dynamics 365 Project Operations helps organizations capture this information while the opportunity is still being developed.This creates an important connection between what sales promises and what the delivery organization eventually needs to provide.Instead of project managers receiving an email saying that sales has apparently sold several weeks of consulting, the approved scope, roles, estimated effort, pricing, dates, and billing conditions can become part of the connected project record.

PROJECT QUOTES AND CONTRACTS
Quotes and project contracts establish the commercial foundation of a customer engagement.A quote represents what the organization proposes to sell. It can include planned work, estimated effort, project roles, pricing, expected dates, and billing conditions.Once the customer accepts the proposal, the project contract records what the customer actually agreed to purchase.This distinction is important because delivery teams should work against the accepted customer commitment rather than an earlier version of the proposal that may have changed during negotiations.Contracts can also establish whether customers are charged according to time worked, a fixed project price, milestones, or other agreed billing arrangements.

PROJECT PLANNING AND WORK BREAKDOWN STRUCTURES
After the customer accepts the project, the promise needs to become an executable plan.Project managers break large outcomes into smaller pieces of work. This structure is commonly called a Work Breakdown Structure, or WBS.For example, a cloud migration project might contain discovery, design, implementation, testing, customer review, deployment, and closure phases.Each part can then contain individual tasks with planned dates, expected effort, responsibilities, and dependencies.Dependencies are particularly important because project activities rarely happen completely independently. Design may depend on discovery. Testing depends on implementation. Customer approval may depend on testing.When one activity changes, project managers need visibility into what that change could mean for the rest of the schedule.

PROJECT MILESTONES
Milestones provide recognizable checkpoints during a project.A milestone might represent design approval, completion of testing, delivery of a major project component, customer acceptance, or another significant event.Unlike normal tasks, milestones typically represent a point in the project rather than a block of working hours.They are useful for communicating progress and can also have commercial importance. In milestone-based engagements, reaching an agreed milestone may trigger part of the customer's billing schedule.This connects project delivery directly with the commercial agreement.

PROJECT TIME TRACKING
Time entries are more than administrative timesheets.When employees record time against specific projects and tasks, the organization gains information about how much effort the work actually requires.Project managers can compare planned effort with actual effort. If discovery was expected to require 40 hours but has already consumed 60 hours, that difference becomes visible while the project is still active.That does not automatically mean the project is failing. The customer environment may simply have been more complicated than expected.The important point is that the organization now has information it can act on rather than discovering the problem after the project has finished.Approved time can also become an important input into project costs and customer billing.

PROJECT EXPENSE MANAGEMENT
Customer projects frequently involve costs beyond employee time.Consultants may travel to customer locations, purchase approved services, or incur other project-related expenses.Dynamics 365 Project Operations can associate these expenses with the relevant customer project instead of allowing them to disappear into disconnected receipts, emails, or financial records.This creates better visibility for project managers and provides finance with clearer information when reviewing project profitability and customer billing.

RESOURCE MANAGEMENT AND STAFFING
A perfect project plan is useless if the required people are unavailable.Resource management connects project requirements with employees and contractors who have the appropriate skills and availability.A project manager may know that a security specialist is required for two weeks without initially knowing which individual will perform the work.Resource management allows organizations to consider both requirements.Someone may have exactly the right technical skills but already be assigned to another customer. Another person might have the necessary expertise and sufficient capacity during the required period.This helps organizations reduce overbooking and make project commitments based on actual resource availability.

RESOURCE BOOKINGS AND CAPACITY
A resource booking reserves part of someone's working capacity for project work.Employees do not necessarily need to be assigned full-time. A consultant might spend three days each week on one customer project while using the remaining capacity for another engagement, training, internal work, or leave.Connecting resource bookings with availability gives organizations a clearer picture of their delivery capacity.This is particularly valuable for consulting organizations and professional services firms where people represent both the primary delivery resource and a significant part of project cost.

SKILLS, ROLES AND PROJECT COSTS
Staffing is not simply about finding someone with an empty calendar.Projects often require specific roles and competencies such as project managers, business analysts, developers, architects, engineers, consultants, or security specialists.The financial impact also matters.A senior specialist may have a different internal cost than a junior consultant. The organization therefore needs to balance skills, availability, delivery quality, and financial performance when staffing projects.Dynamics 365 Project Operations connects these staffing decisions more closely with the overall project plan and financial picture.

PROJECT COSTS AND PROFITABILITY
A project can finish on time and still lose money.Customer revenue represents only one side of the financial equation. Organizations also need to consider employee costs, contractors, travel, software, materials, and other expenses required to deliver the engagement.Dynamics 365 Project Operations helps connect planned and actual project costs with customer pricing.This makes it easier to understand whether the project is consuming more expensive resources or more working hours than originally anticipated.A project can therefore appear successful operationally while becoming less profitable financially.Connecting project delivery and project financial information helps organizations identify this situation earlier.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.