MB-210 study materials
MB-210 study resources

Adventure Works Field Sales: Documents and Collaboration

MB-210 · Put your knowledge to work in context.

All case studies

Adventure Works Field Sales: Documents and Collaboration

Adventure Works has 120 field reps using Dynamics 365 Sales. Reps need SharePoint document management for accounts and opportunities, Microsoft Teams collaboration for deal rooms, and Outlook integration for tracking email. Email runs through Exchange Online. Security requires reps to see documents only for accounts they own, while shared accounts remain visible to the account team. Symptoms: the Documents tab is missing on some records; emails are not appearing in the timeline; Teams chats are not linked to opportunities; server-side sync shows mailbox alerts; and some reps cannot open the Outlook add-in. Constraints: no on-premises SharePoint; use out-of-box configuration; one SharePoint site collection; document libraries per entity; seven-year retention. The company wants minimal training and no custom code.

1. Configure SharePoint document management for accounts and opportunities, including folder structure and permissions.

Read the worked answer

Reasoning: SharePoint integration requires configuring the SharePoint sites and enabling document management for the Account and Opportunity entities. Use one site collection with separate document libraries for accounts and opportunities to keep the structure simple. Enable folder structure so that documents are organized by account and then by opportunity; this reduces clutter and supports retention. Permissions should inherit from SharePoint and be aligned to Dynamics 365 ownership. Because reps should see documents only for accounts they own, do not grant broad site permissions; use SharePoint security groups that mirror the sales team structure. Shared accounts need account-team access, so include the team in the SharePoint group or use item-level sharing carefully. The Documents tab appears only when document management is enabled for the entity and the record has a valid SharePoint location. Test with an owned account and a shared account.

2. Configure server-side sync and the Outlook add-in, and explain how to troubleshoot emails not appearing in the timeline.

Read the worked answer

Reasoning: Server-side sync requires each mailbox to be approved and tested, and the user must have an Exchange Online mailbox. Configure the mailbox record, approve it, and run the test and enable process. For email tracking, ensure the user has server-side sync enabled for email and that the Outlook add-in is deployed. Emails may not appear in the timeline because the mailbox is not approved, the sync direction is wrong, or the correlation method is not set. Check that the email is tracked or that automatic tracking is enabled. The Outlook add-in may fail if the user lacks the required license or if the add-in is not deployed through Microsoft 365. Test by sending an email to a tracked contact and verifying that it appears in the timeline after sync.

3. Configure Teams collaboration and explain why Teams chats may not link to opportunities.

Read the worked answer

Reasoning: Teams integration requires enabling the collaboration features and connecting Dynamics 365 to Teams. Linking a chat to an opportunity depends on the record being enabled for Teams collaboration and the user having a Teams license. If chats do not link, verify that the Teams integration is turned on, the environment is connected, and the record type is configured. Also check that the user is a member of the team or channel and that the chat was created from the record rather than from Teams. For deal rooms, create the Teams channel from the opportunity so that the link is stored. Test with a new opportunity and confirm that the chat appears in the timeline and the Teams channel.