Study guide
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup
Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Product Master and Released Products
1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups
2 Chapter 2: Bills of Materials (BOM) and Formulas
2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling
3 Chapter 3: Product Prerequisites and Dimension Groups
3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups
4 Chapter 4: Additional Product Details and Warehouse Fit
4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions
5 Chapter 5: Inventory Costing and Pricing
5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding
6 Chapter 6: Inventory Journals and Core Transactions
6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals
7 Chapter 7: Inventory Operations, Blocking, and Closing
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification
8 Chapter 8: Quality Management and Nonconformance
8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders
9 Chapter 9: Asset Management: Setup and Maintenance
9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption
10 Chapter 10: Procurement and Sourcing Configuration
10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal
11 Chapter 11: Purchase Order Lifecycle and Consignment
11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders
12 Chapter 12: Landed Cost and Inbound Logistics
12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
13 Chapter 13: Sales Management and Order Processing
13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates
14 Chapter 14: Warehouse Setup and Core Infrastructure
14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences
15 Chapter 15: Warehouse Execution Processes
15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization
16 Chapter 16: Transportation Management and Logistics
16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation
17 Chapter 17: Warehouse Management Mobile App
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation
18 Chapter 18: Master Planning and Planning Optimization
18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup
Key Takeaways Explain This Topic AI
The Warehouse Management mobile app implements a decoupled two-tier security architecture: Microsoft Entra ID authentication for device-to-environment connectivity, and Warehouse Worker credentials (User ID and PIN) for user session execution.
For production RF scanner fleets, X.509 certificate-based authentication is the enterprise standard over client secrets because certificates eliminate recurring secret expirations and prevent plaintext credential compromise on physical devices.
Connection profiles encapsulate the service URL, tenant ID, and client ID, and can be distributed to hundreds of mobile devices instantaneously using configuration QR code scans or Mobile Device Management (MDM) enrollment profiles.
Warehouse workers (work users) must be linked to a Human Resources worker record and configured with a default warehouse, permitted warehouses, and a root mobile device menu.
Work user operational parameters govern critical floor execution permissions, including Allow override location, Allow pick split, Allow manual movement, and Maximum pick quantity.
Last updated: September 2026
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup
Quick Answer: The Warehouse Management mobile app in Microsoft Dynamics 365 Supply Chain Management (D365 SCM) operates on a two-tier security model : device connectivity is authenticated via Microsoft Entra ID (using either a client secret or an X.509 certificate linked to a service principal in D365 SCM's Microsoft Entra applications table), while warehouse floor transactions are authorized via a Warehouse Worker User ID and PIN . Warehouse workers must be explicitly linked to an underlying Human Resources worker record and assigned operational permissions—such as Allow override location , Allow pick split , and Allow manual movement —to govern physical exception handling on the warehouse floor.
1. Warehouse Management Mobile App Architecture
The Warehouse Management mobile app replaces the legacy browser-based Work User portal ( WHSWorkExecute ) with a modern, touch-optimized native application built on cross-platform frameworks. It is designed to run reliably across diverse industrial hardware form factors, including rugged handheld radio frequency (RF) barcode scanners, wearable ring scanners, vehicle-mounted forklift terminals, and commercial tablets or smartphones.
Supported Operating Systems
Windows : Windows 10 (version 1809 or later) and Windows 11, distributed via the Microsoft Store or sideloaded as an MSIX bundle on industrial vehicle-mounted computers.
Android : Android 8.0 or higher, distributed via Google Play or installed directly via APK on enterprise mobile computers (e.g., Zebra, Honeywell, Datalogic).
iOS : iOS 13.0 or higher, distributed via the Apple App Store for Apple devices. ┌──────────────────────────────────────────────────────────────────────┐
- │ Two-Tier Authentication Model │
- └──────────────────────────────────────────────────────────────────────┘
- Tier 1: Device Connectivity Authentication (Environment Level)
- ┌───────────────────────────┐ ┌───────────────────────────┐
- │ Rugged Handheld Scanner │ │ Microsoft Entra ID │
- │ Mobile App Profile │ │ (Azure Active Directory) │
- │ ───────────────────────── │ │ ───────────────────────── │
- │ • Client (App) ID │─────────►│ • Validates App Identity │
- │ • Tenant ID │ OAuth │ • Evaluates Cert / Secret │
- │ • X.509 Cert / Secret │ Token │ • Issues Bearer Token │
- └───────────────────────────┘ └─────────────┬─────────────┘
- │
- ▼
- ┌───────────────────────────┐
- │ D365 SCM Environment │
- │ System administration > │
- │ Microsoft Entra apps │
- │ (Maps Client ID -> User) │
- └─────────────┬─────────────┘
- │
- Tier 2: Operational Worker Authentication (Session Level) │
- ┌───────────────────────────┐ │
- │ Warehouse Worker Signs In │ │
- │ ───────────────────────── │ │
- │ • Work User ID (e.g. WH01)│◄───────────────────────┘
- │ • Numeric PIN / Password │ (Authorizes menu hierarchy, default
- │ • Validated vs WHS Worker │ warehouse, and operational rights)
- └───────────────────────────┘
- The Two-Tier Authentication Architecture
A fundamental concept for the MB-330 exam is the separation between Device Authentication and User Authentication :
Device-Level Authentication (Microsoft Entra ID) : Authorizes the physical application instance to establish an encrypted API handshake with the Dynamics 365 Supply Chain Management environment. No warehouse worker can interact with D365 SCM until this connection is established.
User-Level Authentication (Warehouse Worker) : Once the device connects to the environment, the worker is presented with a login screen requesting a User ID and Password (or numeric PIN). This authenticates against the internal D365 SCM WHSWorkUser table, establishing the worker's operational permissions, language, default warehouse, and available menu hierarchies.
2. Microsoft Entra ID Registration and Connection Profiles
To establish the device-level handshake, a system administrator must register an application in the Microsoft Entra admin center and configure the corresponding service principal in D365 SCM.
Step 1: Azure App Registration in Microsoft Entra ID
Navigate to the Microsoft Entra admin center > Applications > App registrations .
Select New registration , assign a name (e.g., D365-WHS-MobileApp ), and select the supported account type (Single tenant).
Record the Application (client) ID and the Directory (tenant) ID .
Under Certificates & secrets , generate either a Client secret or upload an X.509 public certificate ( .cer ).
Under API permissions , grant the application delegated permissions to access Dynamics ERP ( Ax.FullAccess ).
Step 2: Configure D365 SCM Microsoft Entra Applications
In D365 SCM, navigate to System administration > Setup > Microsoft Entra applications .
Create a new record:
Client ID : Paste the Application (client) ID generated in Microsoft Entra ID.
Name : Enter a descriptive identifier (e.g., WHS Mobile App Service Principal ).
User ID : Assign a dedicated system user account (e.g., WHS_ServiceAccount ). This user must have the Warehouse mobile device user security role and the legal entities assigned where warehouse operations occur.
Client Secret vs. Certificate Authentication
Feature Client Secret Authentication Certificate Authentication (Recommended)
Security Posture Symmetric shared string; vulnerable to extraction if device is lost or compromised. Asymmetric cryptography; private key is installed securely in the device keystore or MDM container.
Expiration & Maintenance Client secrets expire (typically 12 to 24 months). When expired, all scanners halt immediately until manually updated. Certificates can have longer lifespans (3 to 5 years) and support automated deployment and renewal via enterprise PKI.
Deployment Method String embedded in connection JSON payload or QR code. Public key ( .cer ) registered in Entra ID; private key ( .pfx ) pushed to devices via Mobile Device Management (MDM).
Operational Use Case Proof-of-concept, test environments, or non-production sandboxes. Enterprise production fleets of industrial RF scanners (Zebra, Honeywell) managed via Microsoft Intune or SOTI MobiControl.
Connection Profiles and QR Code Enrollment
Rather than manually keying complex URLs, tenant IDs, and client IDs into hundreds of ruggedized scanners, administrators generate connection configurations in JSON format: {
- "ConnectionList": [
- {
- "ActiveDirectoryClientAppId": "00001111-aaaa-2222-bbbb-3333cccc4444",
- "ConnectionName": "USMF Production Warehouse",
- "ActiveDirectoryResource": "https://usmf-prod.operations.dynamics.com",
- "ActiveDirectoryTenant": "https://login.windows.net/tenant-domain.com",
- "Company": "USMF",
- "UseCertificate": true,
- "CertificateThumbprint": "A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0"
- }
- ]
- }
QR Code Scanning : The JSON string is converted into a standard 2D QR barcode. Upon launching the app for the first time, a technician taps Scan settings and scans the printed QR code, instantly provisioning the device connection.
MDM Distribution : Tools such as Microsoft Intune , SOTI MobiControl , or Omnissa Workspace ONE can distribute the connection configuration file directly into the app's sandboxed storage ( com.Microsoft.WarehouseManagement ), eliminating manual scanning entirely.
3. Display Settings, Themes, and Audio/Haptic Feedback
Warehouse environments range from brightly lit retail distribution centers to dimly lit freezers and outdoor lumber yards. The mobile app provides extensive display customization options configured centrally in D365 SCM:
Navigation : Warehouse management > Setup > Warehouse management parameters (and the Mobile device display settings workspace).
Display Customization Capabilities
Themes and Color Schemes :
Light theme : Best suited for standard ambient indoor lighting.
Dark theme : Reduces eye fatigue in low-light environments and preserves battery life on OLED displays.
High-contrast theme : Dramatically enhances readability for outdoor loading docks, cold storage facilities, or workers with visual impairments.
Card Layouts and Screen Scaling :
Field priorities can be established under Warehouse management > Setup > Mobile device > Warehouse app field names to specify which fields appear prominently in the primary card view versus secondary drill-downs.
Supports variable font scaling and full-screen kiosk locking to prevent operators from exiting to the underlying Android/Windows OS.
Step Instructions and Visual Images :
Administrators can define custom, localized, step-by-step instructions for every warehouse operation (e.g., "Scan the pallet license plate on shelf A-01" ).
Product Images : When enabled, the app displays high-resolution released product images during picking or receiving, allowing operators to visually confirm that the physical item matches the scanned barcode.
Audio and Haptic Feedback :
Industrial warehouses are loud environments where screen observation can distract forklift operators. The app utilizes distinct audio chimes and physical vibration patterns:
Success confirmation : Single pleasant chime and short vibration confirming valid scan.
Error / Warning : Harsh low-frequency buzz and double vibration signaling an invalid barcode, location mismatch, or over-pick violation.
4. Warehouse Worker Setup
A Warehouse Worker in D365 SCM represents the operational persona used by a material handler to interact with the mobile app.
Navigation : Warehouse management > Setup > Worker . ┌────────────────────────────────────────────────────────┐
- │ Human Resources Worker (HCMWorker) │
- │ (e.g., John Doe - Emp #1042) │
- └───────────────────────────┬────────────────────────────┘
- │ (Mandatory 1:1 Linkage)
- ▼
- ┌────────────────────────────────────────────────────────┐
- │ Warehouse Work User (WHSWorkUser) │
- │ ────────────────────────────────────────────────────── │
- │ • User ID: WH-JDOE │
- │ • User Name: John Doe │
- │ • Default Warehouse: 24 (Distribution Center) │
- │ • Default Menu: MAIN (Warehouse Root Menu) │
- │ • Password / PIN: •••• │
- │ • Allowed Warehouses:24, 25 │
- └───────────────────────────┬────────────────────────────┘
- │ (Governs Execution)
- ▼
- ┌────────────────────────────────────────────────────────┐
- │ Assigned Work Permissions & Limits │
- │ ────────────────────────────────────────────────────── │
- │ • Allow override location: Yes │
- │ • Allow pick split: Yes │
- │ • Allow manual movement: No │
- │ • Maximum pick quantity: 500 EA │
- └────────────────────────────────────────────────────────┘
- Step-by-Step Setup Procedure
Link to Human Resources Worker : When creating a new warehouse worker, the system prompts for a Worker from the global HR repository ( HcmWorker ). A warehouse work user cannot exist without an associated HR worker record .
Define User Credentials :
User ID : A short alphanumeric string (e.g., WH01 or JDOE ) used to log in at the terminal.
User Name : Display name of the operator.
Password : Numeric PIN or alphanumeric password. Administrators can reset passwords directly from this form.
Assign Default Context :
Default warehouse : The warehouse automatically loaded upon login.
Default menu : The top-level menu node (e.g., MAIN ) presented upon successful authentication.
Assign Allowed Warehouses : Under the Warehouses FastTab, add every warehouse facility the user is permitted to transact in. If a user is not added to a warehouse's allowed list, they cannot select or transact within that facility.
5. Work User Operational Parameters
The Work user record contains critical boolean toggles and threshold parameters that dictate what operational exceptions a worker is permitted to resolve independently:
Work User Parameter Configuration Setting Operational Impact on Warehouse Execution
Allow override location Boolean ( Yes / No ) Permits the worker to deposit inventory into an alternate location during a Put step if the system-directed location is full, blocked, or damaged.
Allow pick split Boolean ( Yes / No ) Allows the worker to split a single picking work line into two lines when the full requested quantity cannot be fulfilled from the directed location.
Allow manual movement Boolean ( Yes / No ) Grants permission to execute ad-hoc, un-directed inventory movements without requiring a pre-existing warehouse work header.
Allow license plate override Boolean ( Yes / No ) Permits the worker to pick inventory from a different license plate than the specific license plate directed by the work header.
Maximum pick quantity Numeric (Quantity) Establishes a maximum threshold of inventory units a worker can confirm in a single transaction, preventing catastrophic data entry errors.
Allow cycle count threshold override Boolean ( Yes / No ) Authorizes a supervisor to accept cycle count discrepancies that exceed standard site or worker percentage/value variance limits.
Allow work cancellation Boolean ( Yes / No ) Enables the worker to cancel open work lines directly from the mobile device interface when an exception occurs.
6. Implementation Scenarios and Exam Traps
Important
Exam Tip — Two Separate User Concepts : Do not confuse a D365 SCM System User ( System administration > Users ) with a Warehouse Worker User ( Warehouse management > Setup > Worker ). System users log into the web browser client using Entra ID credentials. Warehouse workers log into the mobile scanner using a short User ID and PIN. The only bridge between the two is the service account assigned under Microsoft Entra applications that authenticates the mobile app itself.
Warning
Exam Trap — Login Failure Due to Default Warehouse : A common exam scenario describes a worker who can log into the scanner hardware and successfully authenticate to the Entra ID service, but receives the error "User is not authorized for warehouse" when entering their PIN. This occurs when the administrator failed to assign a Default warehouse on the worker profile or neglected to add the warehouse to the Allowed warehouses FastTab.
Tip
Best Practice — Certificate Deployment via MDM : In enterprise environments with hundreds of scanners across multiple shifts, never deploy client secrets. When a secret expires, every terminal across the global supply chain fails simultaneously. Deploy X.509 device certificates managed through automated PKI profiles in Microsoft Intune or SOTI MobiControl.