> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Monitoring for Microsoft Dynamic 365

> Choose between the two GermainUX deployment methods for monitoring browser-based Microsoft Dynamics 365 applications.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)

Availability
2022.1 or later

> [card] [1 Option 1: Deploy the RUM Browser Extension](#1-option-1-deploy-the-rum-browser-extension)
>
> Monitor Dynamics 365 via extension

> [card] [2 Option 2: Deploy RUM JS](#2-option-2-deploy-rum-js)
>
> Direct script on your pages

> [card] [Optional Components](#optional-components)
>
> Add extra Dynamics components

> [card] [Troubleshooting](#troubleshooting)
>
> Resolve Dynamics 365 issues

**Deploy Monitoring for Microsoft Dynamics 365**

## Overview

GermainUX offers two deployment methods for monitoring browser-based Microsoft Dynamics 365 applications:

| Deployment method | Recommended use |
| - | - |
| GermainUX RUM Browser Extension | Microsoft-hosted Dynamics 365 pages where customers cannot modify the top-level application |
| GermainUX RUM JS | Customer-controlled portals, custom pages, web resources, and applications where the monitoring script can be deployed in the required browser context |
| GermainUX Engine | API, application, logs, database level monitoring and automation |
| GermainUX Mobile | Mobile Application and Device monitoring |
| GermainUX RPA Bot Recorder | Synthetic User Scenario Recording |

For standard Microsoft-hosted Dynamics 365 applications, the browser extension is generally required for complete monitoring because customers do not control the top-level application document.

A script deployed inside a web resource or iframe can monitor that component, but it cannot automatically access or monitor the parent Dynamics 365 application when browser security boundaries prevent it.

## Prerequisites

Before deployment:

* Obtain the GermainUX environment URL.
* Create an application entry for Dynamics 365.
* Create or select a UX Monitoring Profile.
* Identify the Dynamics 365 environments and URLs to monitor.
* Define the users, groups, or devices in scope.
* Configure data privacy and Session Replay requirements.
* Confirm that monitored browsers can reach the GermainUX services.
* Test the deployment in a nonproduction environment.

## 1 Option 1: Deploy the RUM Browser Extension

Use the GermainUX RUM Browser Extension to monitor Microsoft-hosted Dynamics 365 applications when RUM JS cannot be added to the top-level page.

![Deploy Monitoring for Microsoft Dynamic 365: 1 Option 1: Deploy the RUM Browser Extension](https://mintcdn.com/germain-ux/hPK2RwO7wyn44bNw/images/main/deploy-monitoring-for-microsoft-dynamic-365/mm5.png?fit=max\&auto=format\&n=hPK2RwO7wyn44bNw\&q=85\&s=fc41fd90ee1f566d6e236ea39f37a741)

The extension is available for supported versions of:

* Microsoft Edge
* Google Chrome
* Mozilla Firefox

### Install the extension

Install the GermainUX extension manually for testing or distribute it through the organization’s browser-management platform.

For production deployments, use an enterprise browser policy such as:

* Microsoft Intune
* Microsoft Edge management policies
* Chrome Enterprise policies
* Group Policy
* Another approved software-distribution platform

Enterprise distribution makes it possible to install and configure the extension consistently across the required user population.

### Configure the extension

Configure the following values:

| Setting | Description |
| - | - |
| GermainUX URL | Base URL of the GermainUX environment |
| Website URL | Dynamics 365 URL or URL pattern to monitor |
| Application Name | Name used to identify the application in GermainUX |
| Profile Name | UX Monitoring Profile applied to the application |

Use the narrowest appropriate URL pattern so monitoring runs only on approved Dynamics 365 applications and environments.

After configuring the extension:

**1. Restart or refresh the browser**

**2. Open Dynamics 365**

**3. Complete a short user scenario**

**4. Confirm that the session and browser telemetry appear in GermainUX**

### Enterprise configuration

When deploying through an enterprise policy:

**1. Add the GermainUX extension to the approved extension list**

**2. Configure forced or managed installation where appropriate**

**3. Apply the configuration to a test user group**

**4. Verify connectivity and data collection**

**5. Validate privacy rules and application scope**

**6. Gradually expand deployment to the required users**

Do not deploy the extension to users or websites outside the approved monitoring scope.

## 2 Option 2: Deploy RUM JS

Use GermainUX RUM JS when the monitored page is controlled by your organization and permits JavaScript deployment.

Applicable examples include:

* Power Pages or customer portals
* Custom Dynamics 365 interfaces
* Customer-controlled HTML pages
* Custom web applications integrated with Dynamics 365
* Web resources where monitoring only that component is sufficient

### Generate the RUM JS configuration

1. Go to **Workspace > Settings > Wizards**.
2. Select the wizard for a standard HTML or browser application.

   ![Deploy Monitoring for Microsoft Dynamic 365: Generate the RUM JS configuration](https://mintcdn.com/germain-ux/hPK2RwO7wyn44bNw/images/main/deploy-monitoring-for-microsoft-dynamic-365/m1.png?fit=max\&auto=format\&n=hPK2RwO7wyn44bNw\&q=85\&s=94003a9e3385b36ce05053e536d61922)
3. Enter the application name and relevant URLs.
4. Select or create the UX Monitoring Profile.
5. Generate or obtain the GermainUX RUM JS loader.
6. Configure the GermainUX service URL and application context.

### Add RUM JS to the application

Add the generated loader to the customer-controlled page according to the application’s deployment process.

Load the script early enough to capture page initialization and subsequent user activity. Ensure that:

* The application’s Content Security Policy permits the script.
* The browser can reach the GermainUX service.
* The script is loaded only once per page context.
* The correct application and environment names are assigned.
* Cache and release procedures are considered.

### Dynamics 365 web resources

RUM JS can be included in a customer-created HTML web resource. However, it monitors only the browser context in which it runs.

If the web resource is loaded inside an iframe, RUM JS can capture activity inside that iframe but may not access the surrounding Dynamics 365 application because of browser origin and security restrictions.

Do not use `eval()` or attempt to bypass iframe, browser, Microsoft, or Content Security Policy restrictions to inject monitoring into a parent page. Use the GermainUX browser extension when access to the top-level Dynamics 365 context is required.

## Optional Components

### GermainUX Engine

Deploy the GermainUX Engine when the monitoring scope includes:

* Synthetic transactions
* API and integration monitoring
* Log or file monitoring
* Infrastructure monitoring
* Scheduled reports
* Automated actions
* Custom data collection

The Engine can collect only data exposed through accessible APIs, logs, files, databases, or infrastructure interfaces. It does not provide access to Microsoft-managed Dynamics 365 server internals.

### RPA Bot Recorder

Deploy the GermainUX RPA Bot Recorder to create synthetic Dynamics 365 scenarios such as:

* Login
* Navigation
* Record search
* Record creation or update
* Case or opportunity processing
* Form submission
* Custom business workflows

The recorded scenarios are executed by a configured GermainUX Engine.

### JS Profiler

Deploy and configure the GermainUX JS Profiler when deeper browser-side JavaScript performance analysis is required. Availability depends on the browser, application security policies, and profiling method.

## Configure Privacy

Before enabling production monitoring:

* Mask sensitive input fields and page content.
* Exclude passwords and authentication data.
* Remove tokens and sensitive URL parameters.
* Exclude confidential pages or components.
* Configure Session Replay sampling.
* Restrict access to user and replay data.
* Define the required retention period.
* Use pseudonymous user identifiers where possible.

Test privacy rules across standard Dynamics 365 pages, forms, dialogs, custom controls, embedded applications, and web resources.

## Validate the Deployment

After deployment:

**1. Open the monitored Dynamics 365 application**

**2. Navigate through several pages and views**

**3. Complete a representative business process**

**4. Generate a controlled browser error where safe**

**5. Confirm that GermainUX receives the session**

**6. Verify page, action, network, and error telemetry**

**7. Open Session Replay, when enabled**

**8. Confirm that sensitive content is masked**

**9. Verify the application, environment, and user context**

**10. Confirm that only approved URLs and users are monitored**

## Troubleshooting

### No data is collected

Verify that:

* The extension or RUM JS is active.
* The Dynamics 365 URL matches the configured pattern.
* The application and profile names are correct.
* The browser can reach the GermainUX service.
* Browser or network policies are not blocking telemetry.
* The user belongs to the deployment scope.
* Monitoring filters do not exclude the session.

### Only a custom component is monitored

RUM JS is probably running inside an iframe or web resource rather than the top-level Dynamics 365 page. This is expected when browser security prevents access to the parent document.

Deploy the GermainUX browser extension when full Dynamics 365 page monitoring is required.

### Session Replay is incomplete

Check whether:

* Some application areas run in separate or cross-origin frames.
* The extension is active on all required Dynamics 365 URLs.
* Privacy rules exclude part of the page.
* Session Replay sampling excluded some sessions.
* Monitoring began after the session had already started.

### The extension does not start

Verify that:

* The extension is installed and enabled.
* Enterprise browser policies permit it.
* Its configuration contains the correct GermainUX and Dynamics 365 URLs.
* The current browser profile is included in the deployment.
* The page was refreshed after installation or configuration.

## Components

* GermainUX RUM Browser Extension
* GermainUX RUM JS
* GermainUX Engine
* GermainUX RPA Bot Recorder
* GermainUX JS Profiler

## Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your SAP environment.

[Contact GermainUX Support](https://docs.germainux.com/main/support.md).

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't find what you need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.