Deploy Monitoring for Microsoft Dynamic 365

🚀 Deploy Monitoring for Microsoft Dynamics 365

📖 Overview

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

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:

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.

The extension is available for supported versions of:

⬇️ 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:

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

🔧 Configure the extension

Configure the following values:

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:

🛠️ Generate the RUM JS configuration

1. Go to Workspace > Settings > Wizards.

2. Select the wizard for a standard HTML or browser application.
   

   

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:

🖼️ 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:

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:

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:

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:

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:

The extension does not start

Verify that:

🛠️ Components

ℹ️ Get More Information

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

Contact GermainUX Support.