Sales mobile and offline in Dynamics 365

The Dynamics 365 mobile experience for sellers runs primarily through the Power Apps mobile app on iOS and Android. The same app that hosts model-driven Power Apps also hosts the Dynamics 365 Sales, Customer Service, and Field Service apps. For sellers in the field — visiting customers, working between meetings, attending events — mobile is the primary work surface.

The Power Apps mobile app. Available free from the Apple App Store and Google Play. Sign in with the user's Microsoft Entra ID; the app discovers which Dynamics 365 model-driven apps the user has access to and lists them. Tap an app, and the experience renders forms, views, and dashboards in a mobile-friendly layout.

Form design for mobile. Model-driven forms render on mobile through the same form designer; mobile-specific properties let the form-designer hide non-critical columns, reorder fields, and use mobile-only forms where the desktop and mobile experiences should diverge. Best practice:

• Show the seller's next actions first — open opportunities, today's meetings, recent activities.
• Hide configuration-style fields that sellers rarely change.
• Keep forms short — three to five sections, not fifteen.

Offline mode. A serious differentiator. The Sales mobile experience supports offline access for configured tables — the seller can browse, edit, and create records without connectivity, syncing when online. The configuration determines:

• Offline profiles per security role — which tables, which views, which related tables, how many records, how recent.
• Filtering — only customer-owned accounts, only opportunities for this seller, only the next 30 days of appointments.
• Storage — bounded by device storage and a configurable limit.

Sync behaviour. Offline data syncs:

• When connectivity returns.
• Periodically in the background.
• On user request from the app.

Sync is incremental — only changes since the last sync are transferred — and uses Dataverse change tracking for efficiency.

Conflict resolution. If the same record is edited offline by the seller and online by someone else, sync detects the conflict and surfaces it for resolution. Default policies (last-writer-wins, client-wins, server-wins) are configurable; complex policies (field-level merge) require custom code.

Outlook and Teams integration. The seller's mobile email and meetings are in Outlook; the Sales app coordinates: opening an email or meeting from a tracked customer shows related CRM context inline. Teams calls and meetings on mobile capture activity records back to CRM if Server-Side Sync and the Dynamics 365 App for Outlook are configured.

Mobile push notifications. Configured Power Automate flows can push notifications to the mobile app — new high-priority lead, opportunity stage change, contract due for renewal, customer satisfied survey response.

Copilot on mobile. Mobile-aware copilot features summarise records, draft replies, and answer questions from the app. The mobile UI is more constrained than desktop; the most valuable copilot uses are short-form (summarise this customer, draft this reply).

Limits.

• Some complex form controls and custom PCF controls don't render identically on mobile; test before assuming parity.
• Offline-mode performance degrades with very large offline data sets; bound the offline profile carefully.
• Some integrations (embedded Power BI, complex iframes) are unfriendly on small screens.

Operational reality. The seller's mobile experience is the seller's daily reality. Spend serious form-design and offline-profile-design time on it — far more than typical for the desktop experience.