MS Learn Highlights – 7/1/2025

Release schedule for proactive quality updates - Finance & Operations

This article explains the release cadence and structure of proactive quality updates (PQUs) for Dynamics 365 Finance and Operations. It also describes how update stations map to geographic regions to manage deployments efficiently.

Summary

• Proactive Quality Updates (PQUs) are releases focused on fixing issues and improving reliability without introducing new features.
• Updates are planned and released regularly to ensure customers get timely fixes.
• Microsoft uses a station-to-region mapping to streamline update rollouts across different geographic areas.
• Understanding the schedule and stations helps IT professionals plan maintenance windows and validate updates against business calendars.

Key Information

Stations and Regions Overview

• Stations are virtual groupings to logically organize update deployments.
• Each station targets a specific region or set of regions.
• Typical regions include North America, Europe, Asia-Pacific, etc.
• Updates are staggered by station to allow for phased validation and issue mitigation.

How to Use This Information

1. Identify your station/region from your service details or admin portals.
2. Monitor the Microsoft Learn and message center for specific dates and update details related to your station.
3. Plan your environment downtime and testing windows around the scheduled update cycles.
4. Use early access stations if you want to test updates before broad deployment.
5. Consult the official schedule regularly to stay informed on upcoming PQUs.

Additional Resources

• Official PQU schedule pages
• Dynamics 365 release notes
• Microsoft message center updates

Original article link:
Release schedule for proactive quality updates - Finance & Operations | Dynamics 365

Advanced load building during wave

This article describes the advanced wave load building feature in Dynamics 365 Supply Chain Management, which improves warehouse outbound processes by automatically assigning shipments to existing waves during wave execution.

Overview

• Purpose: Automate the assignment of shipments to existing active waves based on predefined load building templates during the wave execution process.
• Benefit: Improves efficiency by dynamically building loads (scheduling shipments into trucks or containers) during wave processing, reducing manual intervention.

Key Concepts

• Wave: A group of warehouse orders or shipments processed together to optimize outbound logistics.
• Shipment: A set of items to be shipped together.
• Load Building Template: Rules and criteria defining how shipments are grouped into loads.
• Advanced Load Building: Automatically assigns unassigned shipments into existing waves during wave execution using load building templates.

How Advanced Load Building Works

1. Wave Execution:

   • When a wave is executed, the system evaluates shipments that are not yet assigned to a load.
   • Based on the load building template linked to the wave template, the system automatically assigns shipments to existing waves.

2. Load Building Templates:

   • Templates specify the load size, load mix groups, and other criteria.
   • These templates control how shipments are grouped for transportation.

3. Shipment Assignment:

   • Shipments eligible for load building are automatically assigned to loads adhering to constraints such as maximum weight, volume, or number of cartons.

Configuration Steps

1. Set up Load Mix Groups:

   • Define categories for load types (e.g., pallet types or trailer types).

2. Create Load Building Templates:

   • Define rules for assigning shipments, including load size limits and load mix criteria.

3. Configure Wave Templates:

   • Link load building templates to wave templates for automatic shipment assignment during wave processing.

4. Execute Waves:

   • When a wave is started, the system applies the load building template to assign shipments to loads within the wave.

Benefits

• Dynamic grouping: Adjusts shipment loads in real-time during wave processing.
• Automation: Minimizes manual load assignment, improving warehouse throughput.
• Optimization: Helps maximize load utilization and reduces transportation costs.

For full technical details, configuration, and examples, refer to the original documentation:

Advanced load building during wave - Supply Chain Management | Dynamics 365

User Security Governance Overview

This article provides an overview of user security governance in Microsoft Dynamics 365 Finance & Operations. It explains the security model designed to manage users' access to business data and processes safely and compliantly.

Key Concepts

• User Security Governance ensures that users have appropriate access rights according to their roles and responsibilities in the organization.
• Security is managed via roles, duties, and privileges that define what actions a user can perform and on which data.
• The security model supports segregation of duties, reducing risks of fraud or error by restricting incompatible tasks.
• User access can be governed at granular levels, controlling permissions on forms, fields, business logic, and data.
• Administrators assign security roles to users based on their job functions.
• The framework also facilitates auditing and monitoring to ensure compliance with internal policies and external regulations.

Benefits for Organizations

• Helps enforce consistent security policies across the enterprise.
• Mitigates risks by restricting users' access to only what’s necessary.
• Supports compliance requirements by enabling detailed user activity auditing.
• Enables flexible and maintainable security configurations adaptable to organizational changes.

For detailed technical guidelines on setting up security roles, assigning duties, and managing user access, refer to specific Dynamics 365 documentation.

Original article link:
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/sysadmin/security-gov-overview

Configuration for Finance insights

This article details the configuration steps required to enable and use the capabilities available within Finance insights in Dynamics 365 Finance.

Overview

Finance insights provides AI-driven capabilities that assist in automating and improving financial operations in Dynamics 365 Finance. To use these capabilities, system configuration is needed involving:

• Integration with AI and data services.
• System setup to enable specific Finance insights features.
• Assigning appropriate security roles and permissions.

Configuration Steps

1. Enable the Finance insights service

   • Navigate to the Finance insights workspace in Dynamics 365 Finance.
   • Enable relevant insights features based on your organization's requirements.

2. Set up Azure services and environment

   • Ensure integration with Azure Cognitive Services, Azure Machine Learning, and other necessary Azure components is properly configured.
   • Confirm connectivity and permissions for these Azure services.

3. Configure data entities and data management

   • Enable and manage data entities that feed data into Finance insights.
   • Set up data refresh schedules and verify that data is accurately synchronized.

4. Assign Security Roles and Access Rights

   • Use existing security roles or create custom roles that grant access to Finance insights features.
   • Assign these roles to relevant users to ensure proper access control.

5. Configure AI models and parameters

   • Activate and configure AI models provided by Finance insights, such as cash flow forecasting, accounts payable automation, or vendor invoice prediction models.
   • Configure model parameters according to business needs.

6. Monitor and troubleshoot

   • Use monitoring tools and dashboards provided in Finance insights to verify system health and AI performance.
   • Troubleshoot errors using diagnostic tools and logs.

Additional Notes

• Licensing: Confirm that your Dynamics 365 Finance license includes access to Finance insights features.
• Updates: Regularly update your system for new Finance insights capabilities and improvements.
• Documentation Reference: Detailed AI model configuration and data entity references are available in the official documentation.

Original article for reference:
https://learn.microsoft.com/en-us/dynamics365/finance/finance-insights/configure-for-fin-insites

Security Version Management

This article explains how to manage multiple versions of security configurations within a company using Dynamics 365 Finance & Operations.

Overview

Security version management allows organizations to maintain and manage various versions of security configurations efficiently. This enables scenarios such as:

• Preparing and testing security changes before applying them to production.
• Rolling back to previous security configurations if needed.
• Supporting multiple security setups for different business units or operational stages.

Key Concepts

• Security Versions: Distinct saved states of security configurations including permissions, roles, and duties.
• Version Control: Administrators can create, update, and switch between these versions easily.
• Comparison & Deployment: Versions can be compared for differences and deployed to the active security model after validation.

How to Maintain Multiple Security Versions

1. Create New Security Versions
   • Use the security configuration workspace to create new versions for development or testing.
2. Modify Security Settings in a Version
   • Assign roles, duties, and privileges within the chosen version without affecting active production settings.
3. Compare Versions
   • Analyze differences between versions to understand changes or updates.
4. Switch or Deploy Versions
   • When validated, activate a specific version to become the effective security model.
5. Rollback if Necessary
   • Revert to a previously saved security version to mitigate issues or incorrect changes.

Benefits

• Safer and controlled security configuration changes.
• Facilitates audit and compliance by tracking modifications.
• Reduces downtime and risk by testing security changes offline.

Additional Information

• Supported in Dynamics 365 Finance & Operations environment version 7.0.0 and later.
• Typically managed by system administrators with security configuration roles.

For detailed procedural guidance and UI navigation, consult the official documentation.

Original article link:
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/sysadmin/security-version