Dataverse record change trigger: This trigger is ideal for monitoring changes to records in Dynamics 365, such as when the opportunity status is updated to "Won." By using this trigger, you can initiate the journey to send the "Getting started" email when the specific condition of the opportunity being marked as won is met.

Correct:
* : From the email settings in the Advanced settings, you migrate email router data from server-side synchronization to Dynamics 365 app for Outlook. [See step 1 below. Use Server-side synchronization]
* You test the email configuration and enable the mailboxes for the Dynamics 365 App for Outlook designated users. [Yes, see step 2 below] Incorrect:
* Within the system settings and email configuration, you set Process Email Using to Dynamics 365 for Outlook. [No, set this to Server-side synchronization. See step 1 below] Note:
Deploy and install Dynamics 365 App for Outlook
Step 1: Set the default synchronization method
To use Dynamics 365 App for Outlook, you need to set server-side synchronization for your email processing.
1. From your app, go to Settings > Advanced Settings.
2. Go Settings > Administration and then select System Settings.
3. Select the Email tab, and set Process Email Using to Server-Side Synchronization.
Step 2: Test email configuration and enable mailboxes
Enable and test your user mailboxes so they can use Dynamics 365 App for Outlook.
Reference:
https://learn.microsoft.com/en-us/dynamics365/outlook-app/deploy-dynamics-365-app-for-outlook
Topic 1, Contoso Ltd.
Background information
Contoso Ltd. has started a new division that provides janitorial services to businesses.
The sales teams for this division are using a dedicated instance of Dynamics 365 Sales.
Contoso Ltd.'s sellers are becoming accustomed to Copilot in Sales and Sales Insights features. They have identified several desired enhancements.
System configuration
The base currency for all opportunities in the system is US dollars (USD). The administrator has NOT enabled installed premium Sales Insights features. All users have Premium licenses. Contoso Ltd. uses Exchange Online for email.
Only three default insights cards are turned on:
1 Close date coming soon
2. Meeting today
3. Upcoming meeting
The system administrator has set the following days before notifying me value for the Close date coming soon card to 21 days.
Contoso Ltd. has also just set up Dynamics 365 Customer Insights - Journeys for marketing automation. No segments or customer journeys have been defined yet. Dynamics 365 Sales and Customer Insights - Journeys both share the same instance of Microsoft Dataverse.
Copilot in Dynamics 365 Sales settings
The following screenshots show the configured fields for opportunity settings summaries and recent changes in Copilot.

Business development managers
Contoso Ltd. has 30 business development managers (BDMs) across its sales teams. Each BDM is responsible for selling janitorial services to new and existing clients. All BDMs are assigned the sales manager security role in Dynamics 365 Sales.
Any 8DM can own an opportunity, even if a different BDM owns the client account record. Any other BDMs assigned to work on the opportunity will be included in the opportunity record's sales team. Opportunity records owned by a BDM will never include any additional client stakeholders other than the named contact for the opportunity.
The BDMs have been told to document all client communications in Dynamics 365, but they frequently exchange emails with client contacts through Microsoft Exchange WITHOUT tracking them in Dynamics 365.
Digital sales team
Contoso Ltd. has a digital sales team that comprises 10 junior sales resources who focus on lead qualification and conversion to opportunities. Members of this team are assigned a single custom security role named Digital seller that is a copy of the standard Salesperson role. View audit history and view audit summary permissions are disabled.
The team currently receives leads from an online form on Contoso Ltd.'s website. Many online lead submissions end up being duplicates, and the team manually reconciles the duplicates by comparing last name, email address, and phone number for all submitted leads.
Clients
Contoso Ltd. has a digital sales team that comprises 10 junior sales resources who focus on lead qualification and conversion to opportunities. Members of this team are assigned a single custom security role named Digital seller that is a copy of the standard Salesperson role. View audit history and view audit summary permissions are disabled.
The team currently receives leads from an online form on Contoso Ltd.'s website. Many online lead submissions end up being duplicates, and the team manually reconciles the duplicates by comparing last name, email address, and phone number for all submitted leads.
Client tiers
Clients are grouped into tiers based on annual revenue as calculated in a system outside Dynamics 365 Sales. Clients receive different levels of ongoing service and support based on their tier assignment Annual revenue values for accounts and corresponding tier values are written to Dynamics 365 through a nightly batch process. Client tier values are only updated when they change, and tier value will always be blank for accounts with no calculated annual revenue.
The tier structure is:
* Tier A - annual revenue greater than or equal to $10,000,000 USD
* Tier B - annual revenue greater than $5,000,000 USD and less than $10,000,000 USD
* Tier C - annual revenue greater than $0 USD and less than or equal to $5,000,000 USD The tier label is stored in a custom text field named Client tier(contoso_dienttiei) that contains only a single letter or is blank.
Northwind Traders account
There are three BDMs who frequently work together on large opportunities.
* BDM1 is the account owner for Northwind Traders, a multinational client.
o BDM1 owns all Northwind Traders opportunities with estimated revenue greater than or equal to 51.000,000.
* BMD2 and BDM3 are assisting BDM1 with several opportunities for Northwind Traders in different cities.
o BDM3 owns all other Northwind Traders opportunities. BDM3 is NOT a sales team member for any of the opportunities BDM1 owns, o BDM2 is a sales team member for all Northwind Traders opportunities.
Client Contact1 is the primary contact for the Northwind Traders' account. There are two other client contacts with whom the Northwind account team regularly engages - Client Contacts and Client Contact3.
BDM1 and the Northwind Traders account
BDM1 has been on vacation for two weeks. During vacation, BDM1 did NOT log into Dynamics 365, and BDM2 made the following updates to several open Northwind Traders opportunities.

BMD2 also scheduled an internal meeting with BMD1 for the day they return to discuss a request from the primary contact for the account The meeting has the "London office' opportunity as its regarding value.
Desired enhancements
The global sales lead requests the following enhancements:
1. A "Welcome' email should be sent to the primary contact (or an account when the account first enters any client tier. This email should only be sent to the primary contact once.
2. Account owners should receive immediate notifications in the assistant in Dynamics 365 Sales when accounts change tiers. The notifications should include the account name and current tier.
3. A "Getting started" email should be sent to the main contact associated with an opportunity when the opportunity status is set to "Won."
1. The email should include a link to a custom onboarding form where the contact can supply information required to start the janitorial services for a given location.
2. If the contact does NOT click any links in the email, a follow-up email should be sent
4. All emails between BDMs and client contacts should be available for relationship analytics KPIs. Emails sent by other users outside of Dynamics 365 should NOT be included in the KPIs.
The digital sales team lead requests the following enhancements:
1. The ability for team members to use Copilot to summarize changes to lead records.
2. Replace the current online form used by their team to capture new leads. The new form should automatically handle duplicates using the rules the team currently applies manually.

In Dynamics 365 Sales, security roles control access to different forms, views, and records. To ensure that each department can only access their respective custom forms and views, you should assign security roles to the forms and views. This allows you to restrict users based on their department so they only see the forms and views relevant to them.
How it works:
* Edit the form properties # Assign the form to specific security roles.
* Edit the view properties # Restrict views based on security roles.
* Ensure users have the correct security roles # Users in Department A will only see their assigned forms and views, and the same applies to Department B.

Reference:
Audit User Access:
The Audit User Access checkbox ensures that user activities related to accessing records are tracked. This is essential for identifying when specific users accessed records, which could correlate with field changes observed.
Enabling this option provides insights into who accessed which records and when, which is useful in understanding user behavior and any unusual access patterns.
Additional Steps for Table-specific Auditing (if needed):
After enabling auditing at the system level, specific tables (entities) need to have auditing enabled if they are not covered under common, sales, marketing, or customer service entities.
Go to Settings > Customizations > Customize the System, select the custom table, and ensure that Auditing is enabled on the desired fields within the table.
By enabling both Start Auditing and Audit User Access, you ensure that both data changes and access patterns are recorded, providing a comprehensive audit trail for monitoring and troubleshooting field changes on records.

Correct:
* Transform the first row to be used as headers. Define column types to be the appropriate field types and name the query. Create a full name and full address columns by merging the appropriate columns if they exist. Select Next and your data is now ready for unification.
The proposed solution effectively prepares the data for unification in Dynamics 365 Customer Insights - Data. Here's how each step contributes to meeting the goal:
Transform the first row to be used as headers: This step is necessary to define the column names, which is critical for accurate data interpretation.
Define column types to be the appropriate field types: Specifying the correct data types for each column ensures that the data will be processed correctly during unification, maintaining data integrity.
Create a full name and full address columns by merging the appropriate columns if they exist: This step enhances the dataset by consolidating relevant information into single columns, which can simplify data usage and improve data quality. Merging columns helps ensure that users can easily access essential information without navigating through multiple fields.
Select Next: This indicates that the data transformation steps are completed and the dataset is ready for the unification process.
Incorrect:
* Define column types to be appropriate field types and name the query. Create a full name and full address columns by merging the appropriate columns, if they exist. Select Next and your data is now ready for unification.
Does not address the problem with null values.
* Remove any rows where the primary key is missing, delete any leading or trailing zeros on the primary key, and name the query. Select Next and your data is now ready for unification.
Problem not related to the primary key.
* Transform the first row to be used as headers, and remove any special characters or spaces from header row. Remove rows with missing primary keys and name the query. Select Next and your data is now ready for unification.
Does not address the problem with null values.
* Transform the first row to be used as headers, define column types to be the appropriate field types and name the query. Select Next and your data is now ready for unification.
Solution removes all rows with null values, which can lead to significant data loss, especially if those rows contain important information.
It may compromise data quality by eliminating rows, which can impact analysis and insights.
* Transform the first row to be used as headers, remove rows that contain null values, and name the query. Select Next and your data is now ready for unification.
While the solution includes transforming the first row to be used as headers and naming the query, the step of removing rows that contain null values is problematic.
Removing all rows with null values can lead to significant data loss, particularly if those rows contain relevant information.