BF BF Technology Solutions

Dynamics 365 Support Intelligence Center

A premium, problem-based reference center for supporting Dynamics 365 users, Outlook integration, email tracking, Sales records, Customer Service, Power Automate, dashboards, reporting, and mobile access.

#d365-accessUser Access #d365-outlookOutlook & Email #d365-salesSales & Records #d365-ticketOpen Support Ticket
Step 01 Identify Choose the affected feature
Step 02 Document Capture the error and environment
Step 03 Test Follow the focused checklist
Step 04 Resolve Confirm operation or escalate

Find a Dynamics 365 answer quickly

Search by feature, customer symptom, record type, or error message.

No matching section was found. Try a shorter term such as login, email, opportunity, flow, dashboard, or mobile.
1

What problem is the client reporting?

Select the statement that most closely matches the issue.

User access
👤

User Cannot Sign In

The client receives an organization, disabled-account, authorization, licensing, or security-group error.

#d365-accessTroubleshoot Access
Outlook integration
✉

Email Is Not Tracking

The Dynamics pane, Track, Set Regarding, mailbox synchronization, or email-processing feature is unavailable.

#d365-outlookTroubleshoot Email
Sales records
◆

Opportunity Is Missing

A lead, account, contact, activity, or opportunity cannot be found in the expected view.

#d365-salesFind the Record
Automation
⚙

Workflow Did Not Run

A cloud flow, approval, notification, workflow, or integration did not start or complete.

#d365-automationCheck Automation
Analytics
▥

Dashboard Looks Wrong

A dashboard is blank, stale, filtered incorrectly, slow, or missing expected records.

#d365-reportingCheck Reporting
Mobile
▯

Mobile App Problem

The app does not open, records are unavailable, or mobile performance is poor.

#d365-mobileCheck Mobile
2

Rapid problem finder

Match the customer’s statement to the first area your team should investigate.

👤

“I cannot sign in.”

Capture the exact error, user identity, environment, license, and security-group status.

Access Path
🔒

“I can sign in, but I cannot see anything.”

Review the selected app, security roles, record privileges, ownership, and view filters.

Security Path
✉

“Dynamics is missing from Outlook.”

Check App for Outlook deployment, the user role, mailbox, and server-side synchronization.

Outlook Path
◆

“My opportunity disappeared.”

Check active views, filters, record owner, business unit, team access, and status.

Record Path
⚙

“The automation did not run.”

Check the trigger, run history, connection, owner, permissions, and environment.

Flow Path
▥

“The dashboard is missing data.”

Check dashboard filters, security access, source views, dataset status, and refresh behavior.

Reporting Path
3

User Access & Security

Use this section for sign-in failures, authorization errors, missing apps, missing records, and role-related access issues.

👤 User cannot sign in Organization, authorization, disabled-account, or license issue

Ask the client

“What exact message appears, and which Dynamics 365 environment are you opening?”

Expected result

The user signs in to the intended environment and sees the assigned application.

Likely areas

Identity, license, environment security group, disabled user, or authentication policy.

Support checklist

  1. Record the complete error message and affected sign-in address.
  2. Confirm the client is opening the correct environment and application.
  3. Verify the user exists and is enabled in the organization’s identity directory.
  4. Confirm the required Dynamics 365 license is assigned.
  5. Check whether the environment is restricted by a security group.
  6. Confirm the user is assigned a valid Dynamics 365 security role.
  7. Test in a private browser window after documenting the original behavior.
Escalate when: The account is disabled or locked, the user is not in the environment security group, a license change is required, or identity-policy administration is needed.
🔒 User cannot see or edit records Records, buttons, views, forms, or apps are missing

Ask the client

“Which record, button, view, or application are you trying to access?”

Expected result

The user sees the records and commands required for their assigned business responsibilities.

Likely areas

Security role, privilege depth, ownership, team access, business unit, app access, or filter.

Support checklist

  1. Record the missing item and a working user for comparison.
  2. Confirm the user is in the correct Dynamics application.
  3. Check the active view and all visible filters.
  4. Confirm the record owner and current record status.
  5. Review assigned security roles and team membership.
  6. Compare read, create, write, append, append-to, assign, and share access as applicable.
  7. Use an approved access checker or administrator review before changing security.
4

Outlook & Email Integration

Use this section for App for Outlook, mailbox, email tracking, Set Regarding, and server-side synchronization issues.

✉ Dynamics 365 App is missing from Outlook The pane, add-in, Track, or Set Regarding is unavailable

Ask the client

“Does Dynamics appear under Outlook Apps or More Apps, and does it show an error?”

Expected result

The Dynamics 365 pane opens and presents the available tracking and record options.

Likely areas

Deployment, security role, mailbox, server-side sync, privileges, or authentication.

Support checklist

  1. Confirm the user can access Dynamics 365 in a browser.
  2. Confirm App for Outlook is deployed to the user.
  3. Verify the Dynamics 365 App for Outlook User role or approved equivalent privileges.
  4. Check the user’s mailbox status and server-side synchronization configuration.
  5. Open the Dynamics pane and record the complete displayed error.
  6. Run the Outlook Checker diagnostics where available.
  7. Export the checker logs for administrator review when the diagnostic detects errors.
↗ Email is not tracking Tracking remains pending, fails, or does not create an activity

Ask the client

“Does Track appear, and can you select a record with Set Regarding?”

Expected result

The email is tracked and associated with the intended Dynamics 365 record.

Likely areas

Mailbox sync, app privilege, regarding record, processing error, or email configuration.

Support checklist

  1. Confirm the Dynamics pane opens without an authorization error.
  2. Record the email subject, sender, recipient, and tracking status.
  3. Confirm the intended Regarding record is visible to the user.
  4. Check whether the mailbox is active and configured for server-side synchronization.
  5. Review mailbox alerts or email-processing errors.
  6. Run Outlook Checker and export logs if the issue continues.
⟳ Mailbox or synchronization problem Email, appointments, contacts, or tasks are not synchronizing

Support checklist

  1. Confirm the affected user and mailbox record.
  2. Record whether incoming email, outgoing email, appointments, contacts, or tasks are affected.
  3. Review the mailbox status, alerts, and last synchronization results.
  4. Confirm the mailbox is approved where the organization requires approval.
  5. Verify the correct email-server profile and synchronization method.
  6. Test the mailbox only after recording the current alerts and configuration.
  7. Escalate persistent server-side synchronization errors with the exact alert and timestamp.
5

Sales & Record Management

Use for missing opportunities, leads, accounts, contacts, activities, timelines, and view problems.

◆ Opportunity or lead is missing A record cannot be located in the expected list

Ask the client

“What is the record name, who owns it, and when was it last seen?”

Expected result

The record appears in an appropriate view or search result.

Likely areas

View filter, record owner, status, security, business unit, team access, or deletion.

Support checklist

  1. Capture the exact record name and known identifying information.
  2. Change from the current personal view to an appropriate system view.
  3. Review search text, date restrictions, status, owner, and business-unit filters.
  4. Check active, inactive, won, lost, qualified, and disqualified records as applicable.
  5. Confirm the expected owner and owning team.
  6. Compare access with a user who can see the record.
  7. Escalate security or audit-history review when administrator access is required.
▤ Activities are missing from the timeline Emails, appointments, tasks, notes, or calls do not appear

Support checklist

  1. Confirm the correct parent record is open.
  2. Review timeline filters and selected activity types.
  3. Check the activity owner and Regarding field.
  4. Confirm whether the item was created in Dynamics or synchronized from Outlook.
  5. Check whether the activity is open, completed, canceled, or inactive.
  6. Review security access to the activity and related record.
6

Customer Service & Case Management

Use for cases, queues, assignment, routing, knowledge, and SLA issues.

🎫

Case Is Missing

  • Check active and resolved views
  • Review owner and queue
  • Confirm case number
  • Check security access
  • Review applied filters
⇄

Queue Is Not Updating

  • Confirm queue membership
  • Review queue-item status
  • Check owner assignment
  • Review routing rules
  • Check automation history
◷

SLA Timer Looks Wrong

  • Check applicable SLA
  • Review business hours
  • Confirm holiday calendar
  • Check pause conditions
  • Record timer timestamps
7

Workflows, Approvals & Power Automate

Use for flows, classic workflows, approvals, notifications, and Dynamics 365 integrations.

⚙ Automation did not run The expected flow, approval, or notification did not start

Ask the client

“What action should have started the automation, and which record was involved?”

Expected result

The trigger creates a successful automation run and completes the expected actions.

Likely areas

Trigger conditions, disabled flow, failed connection, owner, permissions, or environment.

Support checklist

  1. Record the affected record and exact triggering action.
  2. Confirm the automation is enabled in the correct environment.
  3. Open run history and locate the expected run.
  4. If no run exists, review the trigger and trigger conditions.
  5. If a failed run exists, record the failed action and complete error.
  6. Check the owner, connection references, credentials, and permissions.
  7. Do not resubmit or duplicate business transactions until the prior run state is understood.
✓ Approval or notification was not sent Approver, Outlook connection, trigger, or recipient issue

Support checklist

  1. Confirm the expected approver or recipient.
  2. Review automation run history.
  3. Check whether the approval action was reached.
  4. Record any Outlook, connector, licensing, or permission error.
  5. Verify the approver address used by the run.
  6. Check spam, quarantine, and alternate notification locations where authorized.
8

Dashboards & Reporting

Use for blank dashboards, stale data, missing records, filter issues, and slow reports.

▥

Dashboard Is Blank

  • Confirm the correct dashboard
  • Review date and owner filters
  • Check source views
  • Compare another authorized user
  • Check browser errors
⟳

Data Is Not Current

  • Record the expected record
  • Check source-system data
  • Review refresh status
  • Check dataset credentials
  • Review synchronization errors
◷

Report Loads Slowly

  • Test another report
  • Test another browser
  • Reduce broad filters
  • Record loading time and scope
  • Escalate repeated performance issues
9

Dynamics 365 Mobile Support

Use for application startup, mobile authentication, missing records, and performance issues.

▯ Mobile application does not open or sign in Authentication, application, network, or device issue

Support checklist

  1. Record the device type, operating-system version, and app version.
  2. Capture the complete sign-in or loading error.
  3. Confirm the user can access the same environment in a browser.
  4. Check whether the mobile device has an active network connection.
  5. Confirm the intended Dynamics application is available to the user.
  6. Review security and mobile-device policies before clearing organizational data.
⌕ Records are missing on mobile The user sees a record in the browser but not in mobile

Support checklist

  1. Confirm the user is in the correct environment and app.
  2. Check whether browser and mobile use the same view.
  3. Review mobile filters and search terms.
  4. Confirm the table and form are included in the application.
  5. Check security access to the record.
  6. If offline access is configured, review the offline profile and synchronization status.
10

Open a Dynamics 365 Support Ticket

Collect this information so BF Technology Solutions can investigate without repeating completed troubleshooting.

Required ticket information

Customer Company and primary contact
Affected User Name and sign-in address
Environment Name and complete environment URL
Application Sales, Customer Service, Outlook, mobile, or custom app
Record Record type, name, and ID when available
Error Complete message, screenshot, or recording
Timeline Date, time, and last known working time
Scope One user, multiple users, one app, or entire environment
Client Platform Browser, Outlook, desktop, or mobile device
Recent Changes Role, solution, flow, mailbox, update, policy, or configuration
Tests Completed Every completed step and its result
Business Impact What the client cannot complete
Request Dynamics 365 Support

BF Technology Solutions

Your Partner in Technology for Dynamics 365, Microsoft 365, Power Platform, managed IT, business process automation, reporting, and connected workplace solutions.

tel:+13177620780Call 317-762-0780 Visit BF Technology Solutions User Access Support Outlook Support Return to Top
This knowledge center is a first-line troubleshooting reference. Security roles, licenses, mailbox settings, environment policies, production automations, solutions, and organizational data should be changed only by authorized administrators under the client’s approved change-control and security procedures.