Transform the way work gets done with Microsoft Copilot in Dynamics 365 Business Central

Transform the way work gets done with Microsoft Copilot in Dynamics 365 Business Central

This article is contributed. See the original author and article here.

In the rapidly evolving AI landscape, Microsoft Dynamics 365 Business Central is taking the lead with innovations that have equipped more than 30,000 small and medium-sized businesses to achieve success. Powered by next-generation AI, Microsoft Copilot offers new ways to enhance workplace efficiency, automate mundane tasks, and unlock creativity. At a time when nearly two in three people say they struggle with having the time and energy to do their job, Copilot helps to free up capacity and enables employees to focus on their most meaningful work.1 

Dynamics 365 Business Central brings the power of AI to small and medium-sized businesses to help companies work smarter, adapt faster, and perform better. AI in Dynamics 365 Business Central improves the way work gets done, enabling you to:

  • Get answers quickly and easily using natural language.
  • Save time by automating tedious, repetitive tasks.
  • Spark creativity with creative content ideas.
  • Anticipate and overcome business challenges.

Reclaim time for important work

In a small or medium-sized business, there is often a lot to do and not many people to help get it all done, so it’s important to make the most of your limited resources to accomplish your goals. Everyday activities like tracking down documents and bringing new employees up to speed can drain your valuable time. What if you had an AI-powered assistant ready to help you find exactly what you need without the hassle?

Available in early 2024, conversational chat using Copilot in Dynamics 365 Business Central helps you answer questions quickly and easily, locate records faster, and even learn new skills—all using natural language. Save time and effort by navigating to documents without having to use traditional menus, and rapidly onboard new users with answers to questions on how, when, or why to do things. Copilot is your everyday AI companion, helping you to speed through tasks, build momentum, and free time for your most impactful work. 

Streamline month-end tasks with enhanced bank reconciliation

Reconciling bank statement transactions with your financial system has often been a tedious monthly chore. Meticulously matching every line item to new or existing accounting entries takes time (and isn’t the most exciting way to spend an afternoon.) In the past, Business Central helped by auto-matching many of the simple one-to-one transactions, but the logic wasn’t able to decipher more complex scenarios such as when multiple charges were paid in a single transaction.

Now, Copilot in Business Central makes bank reconciliation even easier by analyzing bank statements that you import into Business Central, matching more transactions, and proposing entries for transactions that weren’t auto-matched. By comparing and interpreting transaction descriptions, amounts, dates, and patterns across fields, Copilot can help you improve the accuracy of your bank reconciliation while reducing manual effort.

Unlock creativity with marketing text suggestions

Copilot in Business Central helps product managers save time and drive sales with compelling AI-generated marketing text suggestions. Using key attributes like color and material, Copilot can create product descriptions in seconds tailored to your preferred tone, format, and length. Once you’ve made any adjustments, you can easily publish to Shopify or other ecommerce platforms with just a few clicks. Discover how Copilot can help you banish writer’s block and launch new products with ease.

Boost customer service with inventory forecasting

Effective inventory management is crucial in a competitive business environment as it can significantly influence a company’s success and customer retention. This process involves balancing customer service with cost control. Maintaining low inventory reduces working capital, but risks missing sales due to stock shortages. Using AI, the Sales and Inventory Forecast extension uses past sales data to forecast future demand, helping to prevent stockouts. Once a shortfall is identified, Business Central streamlines the replenishment process by generating vendor requests, helping you keep your customers happy by fulfilling their orders on time, every time.  

Reduce risk with late payment prediction

Managing receivables effectively is vital for a business’s financial wellbeing. With the Late Payment Prediction extension, you can reduce outstanding receivables and refine your collections approach by forecasting if outstanding sales invoices are likely to be paid on time. For instance, if a payment is anticipated to be delayed, you could modify the payment terms or method for that customer. By proactively addressing potential late payments and adapting accordingly, you can minimize overdue receivables, reduce risk of non-payment, and ultimately improve your financial performance.

Improve financial stability with Cash Flow Analysis

Powered by AI, Business Central can create a comprehensive Cash Flow Analysis to help you monitor your company’s cash position. Cash flow is a critical indicator of a company’s solvency, and cash flow analysis is an important future-focused planning tool that helps you maintain control over your financial health and make proactive adjustments to meet all your financial commitments. With insights from Business Central, you can pivot quickly to safeguard your company’s fiscal wellbeing, such as obtaining loans to cover cash shortfalls or cutting back on credit when you have surplus cash.

Work smarter with Copilot in Business Central

Copilot in Business Central gives your company an edge with AI-powered innovations that are a catalyst for unleashing human potential, fostering creativity, and driving efficiency in ways previously unimaginable. The integration of AI into everyday business processes is not just about staying ahead in a competitive market, it’s about redefining what’s possible in the workplace. With Business Central, your company is empowered to navigate today’s complex business environment with agility, precision, and a renewed focus on what truly matters.

Customer using a tablet while wearing headphones and working securely remote from a café.

Dynamics 365 Business Central

Work smarter, adapt faster, and perform better with Business Central.


1 Microsoft Work Trend Index Annual Report, May 2023

The post Transform the way work gets done with Microsoft Copilot in Dynamics 365 Business Central appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Azure Managed Lustre with Automatic Synchronisation to Azure BLOB Storage

Azure Managed Lustre with Automatic Synchronisation to Azure BLOB Storage

This article is contributed. See the original author and article here.


This blog post walks through how to setup an Azure Managed Lustre Filesystem (AMLFS) that will automatically synchronise to an Azure BLOB Storage container. The synchronisation is achieved using the Lustre HSM (Hierarchical Storage Management) interface combined with the Robinhood policy engine and a tool that reads the Lustre changelog and synchronises metadata with the archived storage. The lfsazsync repository on GitHub contains a Bicep template to deploy and setup a virtual machine for this purpose.


Disclaimer: The lfsazsync deployment is not a supported Microsoft product you are responsible for the deployment and operation of the solution. There are updates that need applying to AMLFS that will require a Support Request to be raised through the Azure Portal. These updates could effect the stabaility of AMLFS and customer requiring the same level of SLA should speak to their Microsoft representative.

Initial Deployment

The following is required before running the lfsazsync Bicep template:

  • Virtual Network

  • Azure BLOB Storage Account and container (HNS is not supported)

  • AMLFS deployed without HSM enabled

The lfsazsync repository contains a test/infra.bicep example to create the required resources:




To deploy, first create a resource group, e.g.

TODO: set the variables below
az group create –name $resource_group –location $location


Then deploy into this resource group:

az deployment group create –resource-group $resource_group –template-file test/infra.bicep


Note: The bicep file has parameters for names, ip ranges etc. that should be set if you do not want the default values.


Updating the AMLFS settings

Once deployment is complete, navigate to the Azure Portal, locate the AMLFS resource and click on “New Support Request”. The following shows the suggested request to get AMLFS updated:




The lctl commands needed are listed here.


Deploying Azure BLOB Storage Synchronisation

The lfsazsync deployment sets up a single virtual machine for all tasks. The HSM copytools could be run on multiple virtual machines to increase transfer peformance. The bandwidth for archiving and retrieval is constrained to approximately half the network bandwidth available to the virtual machine. It is important to note that the same network will be utilized for both accessing the Lustre filesystem and accessing Azure Storage. This should be considered when deciding the virtual machine size. The virtual machine sizes and expected network performance is available here.


The Bicep template has the following parameters:


Parameter Description
subnet_id The ID of the subnet to deploy the virtual machine to
vm_sku The SKU of the virtual machine to deploy
admin_user The username of the administrator account
ssh_key The public key for the administrator account
lustre_mgs The IP address/hostname of the Lustre MGS
storage_account_name The name of the Azure storage account
storage_container_name The container to use for synchonising the data
storage_account_key A SAS key for the storage account
ssh_port The port used by sshd on the virtual machine
github_release Release tag where the robinhood and lemur will be downloaded from
os The OS to use for the VM (options: ubuntu2004 or almalinux87)


The SAS key can be generated using the following Azure CLI command:

# TODO: set the account name and container name below

start_date=$(date -u +”%Y-%m-%dT%H:%M:%SZ”)
expiry_date=$(date -u +”%Y-%m-%dT%H:%M:%SZ” –date “next month”)

az storage container generate-sas
–account-name $account_name
–name $container_name
–permissions rwld
–start $start_date
–expiry $expiry_date
-o tsv


The following Azure CLI command can be used to get the subnet ID:

# TODO: set the variable below

az network vnet subnet show –resource-group $resource_group –vnet-name $vnet_name –name $subnet_name –query id –output tsv


The following Azure CLI command can be used to deploy the Bicep template (as an alterative to setting environment variables, the parameters could be set in a parameters.json file):

# TODO: set the variables below

az deployment group create
–resource-group $resource_group
–template-file lfsazsync.bicep


After this call completes the virtual machine will be deployed although it will take more time to install and import the metadata from Azure BLOB storage into the Lustre filesystem. The progress can be monitored by looking at the /var/log/cloud-init-output.log file on the virtual machine.



The install will set up three systemd services for lhsmd, robinhood and lustremetasync. The log files are located here:

  • ‘lhsmd’: /var/log/lhsmd.log

  • ‘robinhood’: /var/log/robinhood*.log

  • ‘lustremetasync’: /var/log/lustremetasync.log


Default archive settings

The synchronisation parameters can be controlled through the Robinhood config file, /opt/robinhood/etc/robinhood.d/lustre.conf. Below are some of the default settings and their locations in the config file:


Name Default Location
Archive interval 5 minutes lhsm_archive_parameters.lhsm_archive_trigger
Rate limit 1000 files lhsm_archive_parameters.rate_limit.max_count
Rate limit interval 10 seconds lhsm_archive_parameters.rate_limit.period_ms
Archive threshold last modified time > 30 minutes lhsm_archive_parameters.lhsm_archive_rules
Release trigger 85% of OST usage lhsm_archive_parameters.lhsm_release_trigger
Small file release last access > 1 year lhsm_archive_parameters.lhsm_release_rules
Default file release last access > 1 day lhsm_archive_parameters.lhsm_release_rules
File remove removal time > 5 minutes lhsmd.lhsmd_remove_rules


To update the config file, edit the file and then restart the robinhood service, systemctl restart robinhood.

The lustremetasync service is processing the Lustre ChangeLog continuously. Therefore, actions will happen immediately unless there is a lot of IO all at once where it may take a few minutes to catch up. The following operations will be handled:


  • Create/delete directories

    Directories are created in BLOB storage as an empty object with the name of the directory. There is metadata on this file to indicate that it is a directory. The same object is deleted when removed on the filesystem.

  • Create/delete symbolic links

    Symbolic links are create in BLOB storage as an empty object with the name of the symbolic link. There is metadata on this file to indicate that it is a symbolic link and this contains the path that it is linking to. The same object is deleted when removed on the filesystem.

  • Moving files or directories

    Moving files or directories requires everything being moved to be restored to the Lustre filesystem. The files are then marked as dirty in their new location and the existing files are deleted from BLOB storage. Robinhood will handle archiving the files again in their new location.

  • Updating metadata (e.g. ownership and permissions)

    The metadata will only be updated for archived files that isn’t modified. Modified files will have the metadata set when Robinhood updated the archived file.



Defender EASM – Performing a Successful Proof of Concept (PoC)

Defender EASM – Performing a Successful Proof of Concept (PoC)

This article is contributed. See the original author and article here.

Welcome to an introduction of the concepts and simple approach required for executing a successful Proof of Concept (PoC) for Microsoft Defender External Attack Surface Management (Defender EASM). This article will serve as a high-level guide to help you execute a simple framework for evaluating Defender EASM, and other items to consider when embarking on the journey to understand the Internet exposed digital assets that comprise your external attack surface, so you can view risks through the same lens as a malicious threat actor.


Planning for the PoC 

To ensure success, the first step is planning. This entails understanding the value of Defender EASM, identifying stakeholders who need to be involved, and scheduling planning sessions to determine use cases & requirements and scope before beginning

For example, one of the core benefits of the Defender EASM solution is that it provides high value visibility to Security and IT (Information Technology) teams that enables them to: 

  • Identify previously unknown assets 

  • Prioritize risk 

  • Eliminate threats 

  • Extends vulnerability and exposure control beyond the firewall 

Next, you should identify all relevant stakeholders, or personas, and schedule in 1-2 short planning sessions to document the tasks and expected outcomes, or requirements. These sessions will establish the definition of success for the PoC.  

Who are the common stakeholders that should participate in the initial planning sessions? The answer to that question will be unique to each organization, but some common personas include the following: 

  • Vulnerability Management Teams 

  • IT personnel responsible for Configuration Management, Patching, Asset Inventory Databases 

  • Governance, Risk, & Compliance (GRC) Teams 

  • (Optional) GRC aligned Legal, Brand Protection, & Privacy Teams 

  • Internal Offensive Penetration Testing and Red Teams 

  • Security Operations Teams 

  • Incident Response Teams 

  • Cyber Threat Intelligence, Hunting, and Research Teams 


Use Cases & Requirements 

Based on the scope, you can begin collaborating with the correct people to establish use cases & requirements to meet the business goals for the PoC. The requirements should clearly define the subcomponents of the overarching business goals within the charter of your External Attack Surface Management Program. Examples of business goals and high-level supporting requirements might include: 

  • Discover Uknown Assets 

  • Find Shadow IT 

  • Discover Abandoned Assets 

  • Resulting from Mergers, Acquistions, or Divestitures 

  • Insufficient Asset Lifecycle Management in Dev/Test/QA Environments  

  • Identification of Vulnerabilities 

  • Lack of Patching or Configuration Management 

  • Assignment of Ownership to Assets 

  • Line of Business or Subsidiary 

  • Based on Geographic Location 

  • On-Prem vs Cloud 

  • Reporting, Automation, and Defender EASM Data Integrations 

  • Use of a reporting or visualization tool, such as PowerBI 

  • Logic Apps to automate management of elements of your attack surface 


Prerequisites to Exit the Planning Phase 

  • Completion of the Planning Phase! 

  • Configure an Azure Active Directory or personal Microsoft account. Login or create an account here. 

  • Set up a Free 30-day Defender EASM Trial 

– Visit the following link for information related to setting up your Defender EASM attack surface today for free. 

  • Deploy & Access the Defender EASM Platform 

– Login to Defender EASM 

– Follow the deployment Quick Start Guide 


Measuring Success?

Determining how success will establish the criteria for a successful or failed PoC. Success and Acceptance Criteria should be established for each requirement identified. Weights may be applied to requirements, but measuring success can be as simple as writing out criteria as below:


Requirement: Custom Reporting

Success Criteria: As a vulnerability manager, I want to view a daily report that shows the assets with CVSSv2 and CVSSv3 scores of 10.

Acceptance Criteria:

  • Data must be exported to Kusto

  • Data must contain assets & CVSS (Common Vulnerability Scoring System) scores

  • Dashboards must be created with PowerBI and accessible to user

  • Dashboard data must be updated daily

Validation: Run a test to validate that acceptance criteria has been met.

Pass / Fail: Pass


Executing the PoC 


Implementation and Technical Validation 

We will now look at five different use cases & requirements, define the success and acceptance criteria for each, and validate that the requirements are met by observing the outcome of each in Defender EASM. 


Use Case 1: Discover Unknown Assets, Finding Shadow IT 


Success Criteria: As a member of the Contoso GRC team, I want to identify Domain assets in our attack surface that have not been registered with the official company email address we use for domain registrations.


Acceptance Criteria: 

  • Defender EASM allows for searches of Domain WHOIS data that returns the “Registrant Email” field in the result set.  


  1. Click the “Inventory” link on the left of the main Defender EASM page. 


Figure: Launch the inventory query screen

  1. Execute a search in Defender EASM that excludes Domains registered with our official company email address of ‘’ and returns all other Domains that have been registered with an email address that contains the email domain ‘’.


Figure: Query for incorrectly registered Domain assets


  1. Click on one of the domains in the result set to view asset details. For example, “” domain.

  2. When the asset details open and confirm that the domain ‘’ is in the upper left corner.

  3. Click on the “Whois” tab.

  4. Note that this Domain asset has been registered with an email address that does not match the corporate standard (i.e., “”) and should be investigated for the existence of Shadow IT.


Figure: WHOIS asset details



Use Case 2: Abandoned Assets, Acquisitions


Success Criteria: As a member of the Contoso Vulnerability Management team, who just acquired Woodgrove Bank, I want to ensure acquired web sites using the domain “” are redirected to web sites using the domain “”.  I need to obtain results of web sites that are not redirecting as expected, as those may be abandoned web sites.


Acceptance Criteria:

  • Defender EASM allows for search of specific initial and final HTTP (Hypertext Transfer Protocol) response codes for Page assets

  • Defender EASM allows for search of initial and final Uniform Resource Locator (URL) for Page assets


  1. Run a search in Defender EASM that looks for Page assets that have:

    1. Initial response codes that cause HTTP redirects (i.e., “301”, “302”)

    2. Initial URLs that contain “”

    3. Final HTTP response codes of “200”

    4. Final URL, post HTTP redirect, that do not contain “”


Figure: Query for incorrect page redirection


  1. Click one of the Page assets in the result set to see the asset details.


Figure: Page asset overview

  1. Validate:

    1.  Initial URL contains “”

    2. Initial response code is either “301” or “301”

    3. Final URL does not contain “”

    4. Final response code is “200”




Use Case 3: Identification of Vulnerabilities, Lack of Patching or Configuration Management


Success Criteria: As a member of the Contoso Vulnerability Management team, I need the ability to retrieve a list of assets with high priority vulnerabilities and remediation guidance in my attack surface.


Acceptance Criteria:

  • Defender EASM provides a dashboard of prioritized risks in my external attack surface

  • Defender EASM provides remediation guidance for each prioritized vulnerability

  • Defender EASM provides an exportable list of assets impacted by vulnerability



  1. From the main Defender EASM page, click “Attack Surface Summary” to view the “Attack Surface Summary” dashboard

  2. Click the link that indicates the number of assets impacted by a specific vulnerability to view a list of impacted assets



Figure: Attack Surface Insights Dashboard


  1. Validate that Defender EASM provides additional information about vulnerabilities and remediation guidance.

  2. Click the link in the upper right corner titled “Download CSV report” and validate the contents within



Figure: Vulnerability remediation details




Use Case 4: Assignment of Ownership to Assets, Line of Business or Subsidiary


Success Criteria: As a member of the Contoso GRC team, I need the ability to assign ownership of assets to specific business units through, along with a mechanism to quickly visualize this relationship.


Acceptance Criteria:

  • Defender EASM provides an approach to assigning ownership via labels

  • Defender EASM allows users to apply labels to assets that meet specific indicators that indicate affiliation with a specific business unit

  • Defender EASM provides the ability to apply labels in bulk



  1. Click the “Inventory” link on the left of the main Defender EASM page to launch the search screen

  2. Run a search that returns all Page assets that are on the IP Block “”. The Page assets on this network all belong to the Financial Services line of business, so it is the only indicator of ownership needed in this example.



Figure: Query to determine Page asset ownership by IP Block


  1. Select all assets in the result set by clicking the arrow to the right of the checkbox as shown in the following image and choose the option for all assets.


Figure: Selecting assets for bulk modification


  1. Click the link to modify assets, followed by the link to “Create a new label” on the blade that appears.

  2. A new screen will appear that allows the creation of a label. Enter a descriptive “Label name”, an optional “Display name”, select a desired color, and click “Add” to finish creating a label.


Figure: Link to modify assets and create a label



Figure: Create label detail


  1. After creating the label, you will be directed back to the screen to modify assets. Validate that the label was created successfully.

  2. Click into the label text box to see a list of labels available to choose from and select the one that was just created.

  3. Click “Update”


Figure: Label selected assets


  1. Click the bell icon to view task notifications to validate the status of labels update.


Figure: View status of label update task


  1. When the task is complete, run the search again to validate that labels have been applied to the assets owned by the Financial Services organization.


Figure: Query to validate labels have been applied to assets




Finishing the PoC


Summarize Your Findings

Identify how the Defender EASM solution has provided increased visibility to your organization’s attack surface in the PoC.

  1. Have you discovered unknown assets related to Shadow IT?

  2. Were you able to find potentially abandoned assets related to an acquisition?

  3. Has your organization been able to better prioritize vulnerabilities to focus on the most severe risks?

  4. Do you know have a better view of asset ownership in your organization?



We would love to hear any ideas you may have to improve our Defender EASM platform or where and how you might use Defender EASM data elsewhere in the Microsoft Security ecosystem or other security 3rd party applications. Please contact us via email at to share any feedback you have regarding Defender EASM.


Interested in Learning About New Defender EASM Features?

 Please join our Microsoft Security Connection Program if you are not a member and follow our Private & Public Preview events. You will not have access to this exclusive Teams channel until you complete the steps to become a Microsoft Security Connection Program member. Users that would like to influence the direction/strategy of our security products are encouraged to participate in our Private Preview events. Members who participate in these events will earn credit for respective Microsoft product badges delivered by Credly.



You now understand how to execute a simple Defender EASM PoC, to include deploying your first Defender EASM resource, identifying common personas, how to set requirements, and measure success. Do not forget! – you can enjoy a free 30-day trial by clicking on the link below.

You can discover your attack surface discovery journey today for free.

Copilot in Dynamics 365 Field Service helps take field support to the next level

Copilot in Dynamics 365 Field Service helps take field support to the next level

This article is contributed. See the original author and article here.

This post is co-authored by John Ryan, Manager Functional Architect Dynamics 365 Field Service, Avanade.

One of the most exciting things about the introduction of AI into tools people use every day to do their jobs is the way AI can help revolutionize the way people work. Especially at the frontlines of business, AI provides organizations with innovative and personalized ways to serve customers. According to IDC, 28% of organizations are investing significantly in generative AI.1 This is what’s exciting about the introduction of Copilot in Microsoft Dynamics 365 Field Service.

No doubt about it: modern solutions like Microsoft Dynamics 365 Field Service have already come a long way in helping frontline workers be more productive and efficient in helping customers. But Copilot takes things to the next level by bringing the power of next-generation AI to the frontlines, enabling faster resolution and better service.

Field engineer viewing data after the inspection of turbines on a wind farm.

Streamline Field Service operations with Copilot

Copilot provides a leap forward in the field service space.

Enabling next-level support with Copilot for Field Service in Outlook and Microsoft Teams

Email has long been a critical communications tool for frontline managers and technicians. New data from Microsoft’s 2023 Work Trend Index Annual Report reveals that over 60% of frontline workers struggle with having to do repetitive or menial tasks that take time away from more meaningful work.2 Now, the Copilot in Dynamics 365 Field Service Outlook add-in can streamline work order creation with relevant details pre-populated from emails.

So, what does that mean, exactly? Copilot can also optimize technician scheduling with data-driven recommendations based on factors such as travel time, availability, and skillset. Frontline managers can see relevant work orders and review them before creating new work orders, and they can easily reschedule or update those work orders as customers’ needs change. In addition, organizations can customize work orders for their frontline needs by adding, renaming, or rearranging fields. Even better, Copilot can assist frontline managers with work order scheduling in Microsoft Teams, saving time and effort to find the right worker for the job.

Frontline managers can also easily open the Field Service desktop app directly from the Copilot add-in via Outlook or Teams to view work orders. There, they can see booking suggestions in the work order and book a field technician without opening the schedule board. The booking is created in Microsoft Dataverse and also gets recorded on the Field Service schedule board automatically. All this saves frontline managers valuable time because they can stay in the flow of work, reduce clicks and context-switching between apps, and create work orders quickly without copy/paste errors. In the Field Service app, they can also review work order list views and edit a work order right in the list without having to reopen it.

graphical user interface, text

Getting answers faster with natural language search with Copilot in Teams

Searching work orders to find specific details about customer jobs or looking for information about parts inventory used to mean switching between apps and searching across different sources for information. Now, to search for work orders or other customer data, agents can ask Copilot through a Teams search. They simply ask what they’re looking for using natural language, and Copilot will return specific information related to their work orders in Dynamics 365 Field Service including status updates, parts needed, or instructions to help them complete the job. The more agents use Copilot, the more the AI assistant learns and can assist agents at their jobs. The future is now.

Empowering field technicians with modern user experience

Frontline managers aren’t the only team members getting a productivity boost from more modern tools. The new Dynamics 365 Field Service mobile experience, currently in preview for Windows 10 and higher, iOS, and Android devices, empowers field technicians by giving them all the relevant, most up-to-date information they need to manage work orders, tasks, services, and products and get their jobs done thoroughly and efficiently. This modern user experience supports familiar mobile navigation, gestures, and controls to streamline managing work order Tasks, Services, and Products. Technicians can save valuable time by quickly updating the status of a booking, getting driving directions to a customer site, and changing or completing work order details. They can even get detailed information about tasks with embedded Microsoft Dynamics 365 Guides, which provide step-by-step instructions, pictures, and videos.

Changing the game for frontline technicians with Copilot in mobile

For field service technicians, having Copilot generate work order summaries that include concise, detailed descriptions of services as well as pricing and costs is a game changer. Work order summaries are generated by Copilot on the fly, synthesizing information from various tabs and fields to break down tasks, parts, services, and problem descriptions into a simple narrative, making it easy for technicians to understand job requirements. And because field technicians often need to work with their hands, they can use the voice-to-text feature to update work orders by describing details including exactly what they did on a job, when they started and finished, and what parts they used. When the work is completed, they can use the app to collect a digital signature from the customer or use voice-to-text to capture customer feedback.

Copilot in Dynamics 365 Field Service is a leap forward in the field service space. Can’t wait to see what’s next!

Learn more about the AI-powered experiences in Dynamics 365 Field Service, Teams, and Microsoft’s mixed reality applications for your frontline workforce announced at Microsoft Ignite 2023:

[1] IDC Analyst Brief sponsored by Microsoft, Generative AI and Mixed Reality Power the Future of Field Service Resolution (Doc #US51300223), October 2023

[2] The Work Trend Index survey was conducted by an independent research firm, Edelman Data x Intelligence, among 31,000 full-time employed or self-employed workers across 31 markets, 6,019 of which are frontline workers, between February 1, 2023, and March 14, 2023. This survey was 20 minutes in length and conducted online, in either the English language or translated into a local language across markets. One thousand full-time workers were surveyed in each market, and global results have been aggregated across all responses to provide an average. Each market is evenly weighted within the global average. Each market was sampled to be representative of the full-time workforce across age, gender, and region; each sample included a mix of work environments (in-person, remote vs. non-remote, office settings vs. non-office settings, etc.), industries, company sizes, tenures, and job levels. Markets surveyed include: Argentina, Australia, Brazil, Canada, China, Colombia, Czech Republic, Finland, France, Germany, Hong Kong, India, Indonesia, Italy, Japan, Malaysia, Mexico, Netherlands, New Zealand, Philippines, Poland, Singapore, South Korea, Spain, Sweden, Switzerland, Taiwan, Thailand, United Kingdom, United States, and Vietnam.

The post Copilot in Dynamics 365 Field Service helps take field support to the next level appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Personal Desktop Autoscale on Azure Virtual Desktop generally available

Personal Desktop Autoscale on Azure Virtual Desktop generally available

This article is contributed. See the original author and article here.

We are excited to announce that Personal Desktop Autoscale on Azure Virtual Desktop is generally available as of November 15, 2023! With this feature, organizations with personal host pools can optimize costs by shutting down or hibernating idle session hosts, while ensuring that session hosts can be started when needed.

Personal Desktop Autoscale

Personal Desktop Autoscale is Azure Virtual Desktop’s native scaling solution that automatically starts session host virtual machines according to schedule or using Start VM on Connect and then deallocates or hibernates (in preview) session host virtual machines based on the user session state (log off/disconnect).

The following capabilities are now generally available with Personal Desktop Autoscale:

  • Scaling plan configuration data can be stored in all regions where Azure Virtual Desktop host pool objects are, including Australia East, Canada Central, Canada East, Central US, East US, East US 2, Japan East, North Central US, North Europe, South Central US, UK South, UK West, West Central US, West Europe, West US, West US 2, and West US 3. It needs to be stored in the same region as the host pool objects it will be assigned to, however, we support deploying session host virtual machines in all Azure regions.

  • You can use the Azure portal, REST API, PowerShell to enable and manage Personal Desktop Autoscale.

The following capabilities are new in public preview with Personal Desktop Autoscale:

  • Hibernation is available as a scaling action. With the Hibernate-Resume feature in public preview, you will have a better experience as session state persists when the virtual machine hibernates. As a result, when the session host virtual machine starts, the user will be able to quickly resume where they left off. More details of the Hibernate-Resume feature can be found here.

Getting started

To enable Personal Desktop Autoscale, you need to:

  • Create a personal scaling plan.

  • Define whether to enable or disable Start VM on Connect.

  • Choose what action to perform after a user session has been disconnected or logged off for a configurable period of time.

  • Assign a personal scaling plan to one or more personal host pools.

A screenshot of a scaling plan in Azure Virtual Desktop called “fullweek_schedule”. The ramp-down is shown as repeating every day of the week at 6:00 PM Beijing time, starting VM on Connect. Disconnect settings are set to hibernate at 30 minutes. Log off settings are set to shut down after 30 minutes.A screenshot of a scaling plan in Azure Virtual Desktop called “fullweek_schedule”. The ramp-down is shown as repeating every day of the week at 6:00 PM Beijing time, starting VM on Connect. Disconnect settings are set to hibernate at 30 minutes. Log off settings are set to shut down after 30 minutes.

If you want to use Personal Desktop Autoscale with the Hibernate-Resume option, you will need to self-register your subscription and enable Hibernate-Resume when creating VMs for your personal host pool. We recommend you create a new host pool of session hosts and virtual machines that are all enabled with Hibernate-Resume for simplicity. Hibernation can also work with Start VM on Connect for cost optimization.

You can set up diagnostics to monitor potential issues and fix them before they interfere with your Personal Desktop Autoscale scaling plan.

Helpful resources

We encourage you to learn more about setting up autoscale and review frequently asked questions for more details on how to use autoscale for Azure Virtual Desktop. You may also find these resources helpful: