Introduction
The Dynaway Mobile Client integrates seamlessly with Microsoft Dynamics 365 for Finance and Operations (D365FO)" . The Mobile Client can be used on mobile devices for various types of Asset Management registrations, depending on your company's requirements.
The Mobile Client is installed and set up in Microsoft® Azure® and in the Dynaway mobile module in Microsoft Dynamics® 365 for Finance and Operations.
- Prerequisites
Before you can set up an environment with Dynaway Mobile for Asset Management (AM), your company must have access to:
- a Microsoft® Dynamics Lifecycle Services (LCS) project for Microsoft Dynamics® 365 for Finance and Operations
- a Microsoft® Azure™ subscription Global Administrator
- a Dynaway Mobile for AM license file
- Audience
-
Sysadmin, Partner Consultant
The Dynaway Mobile Client provides mobile access for your workers to work on work orders, as well as other tasks related to the maintenance department. We offer a wide variety of features and modules to help you optimize maintenance management in your company. Here are some of the features and modules available on our mobile client:
- Work on work orders, including
- Checklists
- Fault registration
- Downtime registration
- Consumption registration
- Purchase requisitions
- View and manage asset data
- Maintenance requests
- Scheduling board (separate application)
- Offline inventory
- Offline assets
Refer to our website to learn more about how you can increase flexibility and efficiency by using the Dynaway mobile client with your D365FO Asset management solution:
Mobile Work Order Execution
Scheduling board on the mobile client
Maintenance requests on the mobile client
The Dynaway mobile solution is hosted on Microsoft® Azure® as a web app and uses Microsoft Entra ID for application and user authentication. Below you see an example of a typical setup. Arrows indicate direction of connection initialization.
Azure setup for mobile client
Refer to our FAQ section to learn more about:
- What Dynaway Mobile can do for your maintenance organization.
- Management of user data in the mobile client.
This installation guide applies to Dynaway mobile version 2610.1 and later.
This guide walks you through installing the Dynaway mobile server and mobile applications into your own Azure subscription using the guided installation wizard. The guide is intended for anyone setting up Dynaway mobile for the first time, including new customers and existing customers using this installation process for the first time.
Note: An advanced installation option is available for IT teams that want to automate the installation. For more information, see the README.md file included with your installation bundle.
Before you start the installation, make sure that you have the following:
- A Windows, macOS, or Linux machine with internet access to Azure.
- PowerShell 7 or later. To check your PowerShell version, run
pwsh --version. Windows PowerShell 5.1 is not supported.
- The following Azure PowerShell modules. The installer checks whether these modules are available and offers to install any missing modules.
Az.Accounts
Az.Resources
Az.Websites
- Bicep CLI and Azure CLI. The installer checks for and installs these tools if they are missing. If you use macOS or Linux, install Azure CLI before starting the installation.
- Note: Installing Azure CLI may require administrator rights on your machine. If the installer cannot install Azure CLI because you do not have the required rights, ask your IT department to install it or run the installer from an elevated PowerShell session.
- The installation bundle, containing the following. Keep all the files in the same folder.
Install-Dmo.ps1
main.bicep
- the package
.zip file
- the README file
Make sure that you have the following access and permissions:
- Azure subscription access
- You must have at least Contributor access to the target resource group.
- If the resource group does not exist, you must have Contributor access at the subscription level so that the installer can create it.
- Microsoft Entra ID rights
- If you create a new app registration, you must have Application Administrator or Cloud Application Administrator rights.
- If you reuse an existing app registration, you must be an Owner of that app registration.
- Global Administrator
- Identify a Global Administrator in your organization before starting the installation.
- You may need the administrator to grant consent to the Dynaway mobile during the installation.
- Key Vault permissions
- If you use AI features or the Enhanced barcode/QR scanner, you must have Owner, User Access Administrator, or Role-Based Access Control Administrator permissions on the Key Vault.
- If you do not have the required Key Vault permissions, you can still complete the installation. You can grant the required access manually after the installation.
Ensure you have the following information handy. Check with your organization's IT department or IT/D365 implementation partner who can provide the following information:
- Azure Tenant ID (see screenshot 01 & 02)
- Azure Subscription ID (see screenshot 03 & 04)
- DFO domain, for example,
https://contoso.operations.dynamics.com
- App Service name and Resource group name, if you reuse an existing Azure App Service (see screenshot 05 & 06).
- App registration Client ID, if you reuse an existing Azure app registration (see screenshot 07 & 08).
- Key Vault name or URL, if you plan to use AI features or the Enhanced barcode/QR scanner (see screenshot 09 & 10).
- Blob storage account name and access key, if your setup stores documents in blob storage (see screenshot 11 & 12). You can skip this and add it later. Treat the access key like a password.
- Note:
- Configuring the secrets stored in the Key Vault is a separate post-installation step and is outside the scope of this installation guide. For information about the required Key Vault values, see Key Vault Setup.
- Contact your Dynaway representative for assistance with this configuration.
01: Azure services page with navigation to Microsoft Entra to find the Tenant ID.
02: Azure 'Tenant ID'.
03: Azure services page with navigation to 'Subscriptions' to find the Subscription ID.
04: Azure 'Subscription ID'.
05: Azure services page with navigation to 'App Services' to find the app service Name and Resource group.
06: App service 'Name' and 'Resource group'.
07: Azure services page with navigation to 'App registrations' to find the App registration Client ID.
08: 'Application (client) ID'.
09: Azure services page with navigation to 'Key vaults' to find the Key vault URL.
10: Key 'Vault URI'.
11: Azure services page with navigation to 'Storage accounts' to find the storage account name and access key.
12: 'Storage account name' and access 'key'.
- Step 1: Open PowerShell and go to your bundle folder
- Step 2: Run the installer
- Step 3: Send the consent link to your Global Administrator
- Step 4: Verify your installation
To open PowerShell and go to your installation bundle:
- Open PowerShell 7.
- Go to the folder that contains your installation bundle.
- For example:
cd C:\dmo-install
- Make sure that the installation bundle contains the following files (see screenshot 01). Keep all the files in the same folder.
Install-Dmo.ps1
main.bicep
- the package
.zip file
- the README file
01: Installation bundle folder.
To run the installer:
- In PowerShell, run the following command:
.\Install-Dmo.ps1
- Follow the prompts displayed by the installer.
- The installer asks you to provide the following information (see screenshot 01):
- Azure subscription
- A short name for the installation. This name becomes part of your site's web address, for example,
dmo-contoso-prod.
- DFO domain
- Key Vault details, if required
- Blob storage details, if required
- When choosing the installation name, use a short, lowercase name.
- If the name is already in use in Azure, the installer automatically adds unique characters to the name and displays the final address. You do not need to take any additional action.
- The installer signs you in, creates the required Azure resources, deploys the package, and configures the installation.
- The installation usually takes a few minutes, but it may take longer depending on your Azure environment.
- When the installation is complete, the installer displays the following information (see screenshot 02):
- Site address
- Consent link to send to your Global Administrator
- Summary of what was created
Important: The installation is not yet usable. Continue to the next step to complete the required manual action.
01: Dynaway mobile installation wizard.
02: Installation details displayed after the installer completes.
The Dynaway mobile requires permission to access Dynamics 365 on behalf of your users. A Global Administrator or Privileged Role Administrator must grant this permission.
If consent is required:
- Copy the consent link displayed by the installer.
- Send the link to your Global Administrator or Privileged Role Administrator.
- Ask the administrator to open the link and sign in.
- Select Accept to grant the required permission. The consent link has a format similar to:
https://login.microsoftonline.com/<tenant>/adminconsent?client_id=<id>
Note:
- If you reused an existing app registration during installation and consent was already granted, you can skip this step. The installer displays a consent link only when consent is required.
- Consent is required only once for the installation. You do not need to repeat this step when updating the installation in the future.
- Until consent is granted, users who open the site may see a sign-in or permission error. This is expected and is resolved after the consent is granted.
To verify the installation:
- Open the site address provided by the installer in a browser. Your Dynaway project contact can confirm the exact application path. The address has a format similar to:
https://<your-name>.azurewebsites.net/<app-name>/
- Verify that the application's sign-in page is displayed (see screenshot 01).
- Note:
- It may take some time for the application to become fully available after installation. If the site does not load immediately, wait a few minutes and try again.
- If you see a blank page or an error immediately after installation, check whether the consent step has been completed and whether all required values were entered correctly.
You can refer to Troubleshooting section below to resolve common known issues.
01: Dynaway mobile sign-in page.
| Issue |
Solution |
| A sign-in or permission error is displayed on the site. |
The Global Administrator may not have completed the consent step. |
| A blank page or error is displayed immediately after installation. |
A required value, such as the DFO domain, may be missing or incorrect. Blob storage details may also be incorrect. Run the installer again with the correct values. |
| A required PowerShell module, Bicep, or Azure CLI tool is missing. |
The installer normally offers to install the missing tool. Select y when prompted. |
| The site name is already taken. |
The installer automatically selects a unique alternative name and displays the final address. No action is required. |
| You do not have permission to create an app registration. |
Provide an existing app registration ID or ask an administrator to create an app registration. Contact your Dynaway representative for guidance if required. |
Could not automatically grant access to the Key Vault is displayed. |
You may not have the required Key Vault permissions. Refer to Access and permissions in the prerequisites. The installation can still be completed. The installer displays the manual steps required, or the Key Vault owner can grant the required access. |
| A resource cannot be reached or a download is blocked. |
Your organization's network may restrict outbound access. Contact the person responsible for your network settings. |
| Other issues |
If the issue is not covered here, save the complete output displayed in PowerShell and contact your Dynaway representative. The output can help identify what went wrong. |
Need help?
Contact your Dynaway representative if you encounter an unexpected issue during installation.