MS Learn Highlights – 6/11/2025

Secure One-Box Development Environments in Dynamics 365

This document outlines methods for securing one-box developer environments for Microsoft Dynamics 365 Finance and Operations, including default configurations and custom virtual network deployment.

Key Concepts

• One-Box Development Environment: A single-instance setup for development and testing that minimizes resource use by consolidating all necessary components into one instance.
• Security Configuration: Effective strategies to secure development environments against threats.

Default Configuration Aspects

• User Roles: Utilize least privilege principle to assign roles.
• Networking: Employ Azure Virtual Networks (VNET) for isolating resources.
• Access Control: Implement strong authentication mechanisms.

Deploying to a Custom Virtual Network

1. Setup Azure Virtual Network: Create a new VNET in Azure to host your one-box environment.
2. Integrate with One-Box:
   • Modify the configuration of your one-box instance to connect to the new VNET.
   • Ensure required resources (e.g., databases, compute) are accessible through the VNET.
3. Test Connectivity: Validate connections and performance within the VNET setup.

Security Best Practices

• Regularly patch and update the environment.
• Enforce data encryption in transit and at rest.
• Conduct periodic security audits and compliance checks.

For detailed technical implementation, refer to the complete article.

Original Article Link

Work Order Project Setup in Dynamics 365 Supply Chain Management

The article provides detailed instructions on setting up work order projects in Asset Management within Dynamics 365 Supply Chain Management. It focuses on the configurations required for managing work order jobs effectively.

Key Steps for Setting Up Work Order Projects:

1. Navigate to Work Order Setup:

   • Access the Asset Management module.
   • Go to Work Orders > Work Order Projects > Project Setup.

2. Define Project Parameters:

   • Input the necessary identifiers and descriptions for the project.
   • Configure key project settings such as project type and related workflows.

3. Set Up Job Codes:

   • Create job codes relevant to the projects.
   • Include details such as job descriptions, units of measure, and cost allocation.

4. Assign Project Resources:

   • Determine required resources for each work order job.
   • Allocate teams or individuals to specific tasks related to the project.

5. Save and Validate Setup:

   • Review the entries for accuracy.
   • Save the configuration and ensure that all data aligns with organizational standards.

Additional Considerations:

• Ensure that any automated workflows that are dependent on these projects are linked appropriately.
• Regularly update project parameters as needed based on operational feedback.

For detailed instructions and further insights, visit the original article: Work order project setup - Supply Chain Management | Dynamics 365.

Approvals Overview in Microsoft Dynamics 365 Project Operations

This document provides an overview of the approvals feature within Microsoft Dynamics 365 Project Operations, detailing its functionality for streamlining approval processes.

Key Features of Approvals

• Workflow Integration: Approvals are integrated into various workflows in Project Operations, enabling efficient request submissions for approvals.
• Role-Based Access: Users can manage approvals based on their roles within the organization, ensuring appropriate access and controls.
• Notifications and Alerts: Automated notifications inform users of pending approvals, improving response times and workflow efficiency.

Approvals Process

Approvals within Project Operations typically involve the following steps:

1. Submission: A user submits a request that requires approval.
2. Notification: The designated approver receives a notification about the pending request.
3. Review: The approver reviews the submitted request and can access relevant information.
4. Decision: Once reviewed, the approver can either approve or reject the request.
5. Completion: The status of the request updates accordingly (approved/rejected), and the initiating user is notified of the outcome.

Impact

• Enhances collaboration by clarifying the approval chain.
• Increases accountability through recorded actions and responses.

Get Started with Approvals

To begin using the approvals feature:

• Ensure you have appropriate permissions set as per your organizational role.
• Access the approvals interface within Microsoft Dynamics 365 Project Operations to start managing your requests.

For more detailed guidance and resources, refer to the original article: Approvals overview.

Create and Confirm Entry Journals in Microsoft Dynamics 365 Project Operations

This article describes the process of creating and confirming Entry journals in Microsoft Dynamics 365 Project Operations.

Steps to Create Entry Journals

1. Navigate to the Entry Journals Page:

   • Go to the Actuals section.
   • Select Entry Journals.

2. Create New Entry Journal:

   • Click on New to create a new entry journal.
   • Fill in the relevant fields:
     • Name: Enter a unique name for the journal.
     • Description: Provide a description of the journal.

3. Add Entries to the Journal:

   • Click on Add Entries.
   • Input the necessary details for each entry, such as:
     • Date
     • Amount
     • Project ID
     • Task ID

4. Save the Journal:

   • Once all entries are added, click on Save to ensure your changes are stored.

Steps to Confirm Entry Journals

1. Select the Journal:

   • Find and select the journal you want to confirm from the Entry Journals list.

2. Review Journal Details:

   • Make sure all entries are correct and complete.

3. Confirm the Journal:

   • Click on the Confirm button to finalize the journal.

4. Verify Confirmation:

   • Check the status of the journal to ensure it has been confirmed successfully.

Important Notes

• Ensure that all required fields are filled accurately before saving or confirming journals.
• Confirming journals prevents further modifications to the entries.

For more detailed guidance and best practices, refer to the original article.

Original Article Link

Adding Required Custom Fields to Price Setup and Transactional Entities

This article outlines the process for adding required custom field references to entities, forms, and views within Microsoft Dynamics 365 Project Operations. These custom fields are essential for ensuring that price setup can accommodate specific business needs.

Steps to Add Custom Fields

1. Navigate to the Field Definition Area:

   • Open the Project Operations app.
   • Go to Settings, then select Customizations.

2. Create a New Custom Field:

   • Click on Field Definitions.
   • Select New to create a new custom field.

3. Define Custom Field Properties:

   • Specify the Field Name, Data Type, and any additional properties.
   • Mark the field as Required if applicable.

4. Associate the Custom Field with Entities:

   • Go to the Entity Configuration section.
   • Choose the entity to which you want to add the custom field.
   • Click on Fields and select the custom field you created.

5. Update Forms and Views:

   • Navigate to Forms or Views under the entity configuration.
   • Add the custom field to the desired forms/views for visibility.

6. Publish Customizations:

   • Once all changes are made, click on Publish to ensure the custom fields are available.

7. Verify Custom Field Integration:

   • Check the forms and views where you added the custom field to ensure it displays correctly and is functional.

Key Considerations

• Ensure that the custom fields meet the business requirements for pricing structures.
• Regularly test the integration of custom fields in transactional scenarios to avoid disruptions.

For further reference or detailed instructions, visit the original article: Add required custom fields to price setup and transactional entities.