Set up device fingerprinting

A device fingerprint, also known as a machine fingerprint, contains information that is collected about a remote computing device, such as a computer, Xbox, tablet, or smartphone, for the purpose of identifying that device. Device fingerprinting lets you collect crucial device telemetry during online actions. This information includes hardware information, browser information, geographic information, and the Internet Protocol (IP) address.

Microsoft Dynamics 365 Fraud Protection provides a device fingerprinting feature that is based on artificial intelligence (AI). Therefore, device identification can be used as input to the process of fraud assessment. Additionally, this feature helps the Fraud Protection service track and link seemingly unrelated events in the fraud network, to help identify patterns of fraud. The data that is collected is not just a static list of attributes but also includes data that is dynamically captured based on the evaluation of specific combinations of attributes, such as browser, system, network, and geo-location attributes. When device characteristics and attributes are collected, the device fingerprinting service uses machine learning to probabilistically identify the device.

Device fingerprinting runs on Azure, and includes benefits from proven cloud scalability, reliability, and enterprise-grade security. To help you better understand the impact that device fingerprinting has on fraud detection, this document includes some results from a study that Microsoft did. The study compared six months' worth of data for various Microsoft businesses through two different models: one that used device fingerprinting and one that did not.

In summary, the results showed that device fingerprinting has a significant positive impact on the model detection rate for all businesses. Because it reduces false negatives, less fraud is detected on approved transactions after the fact.


The purpose of this set up guide is to help you complete the following steps in your own system and with your own data:

  • Map a customer's journey to a risk assessment action (for example, a checkout process or an account creation page) by making a device fingerprinting call to trigger a profiling service. This call includes a Fraud Protection customer-defined session ID and customer ID.
  • Receive a response from the profile service. This response includes a list of device data that Fraud Protection should collect from the event.
  • Run the device fingerprinting script, collect the required information, and send it to Fraud Protection.
  • Assess this user's transactions for fraud, make the appropriate assessment API call, and pass the session ID to Fraud Protection.
  • Fraud Protection then associates the captured device fingerprint information with the transaction that is being assessed.


Before you begin the tasks in this document, you must set up Fraud Protection in an Azure Active Directory (Azure AD) tenant, as described in Set up a trial version of Fraud Protection and Set up a purchased version of Fraud Protection.

It is your responsibility to:

  1. Inform your customers of your data processing practices, for example by disclosing the data you collect and how it is used.
  2. Disclose your use of third parties working on your behalf to process the data you collect, including Fraud Protection service providers.
  3. Comply with all laws and regulations applicable to its use of Fraud Protection, including data protection laws.

Important notice regarding data collection

When you implement Fraud Protection device fingerprinting by integrating the script on your online services, you direct Microsoft to collect the following types of data from the devices interacting with such services:

  • Device attributes such as plugins installed, processor class, etc.
  • Operating system attributes, such as OS Information.
  • Browser-related attributes if applicable such as browser language, font, etc.
  • Network attributes, such as IP address, signature hash, etc.

Set up DNS and SSL certificate

Set up DNS by following these steps:

  1. Select a subdomain under your root domain.For example, select Any prefix can be used.

  2. For the selected subdomain, create a canonical name (CNAME) that points to example, Merchant website:, DNS record:, which points to

Set up the Secure Sockets Layer (SSL) certificate by following these steps:

  1. For back-end onboarding, generate the SSL certificate for the selected subdomain. You can add all the subdomains in Certificate’s Subject Alternative Name and create one SSL Certificate.

  2. After you generate the SSL certificate, Microsoft will need your SSL certificate and private key for onboarding. To start the process of exchanging SSL certificates, email

Implement device fingerprinting

Your website or application should enable the device fingerprinting before it submits a transaction (such as a transaction for adding a payment instrument, sign-in, or checkout). Follow these steps to integrate device fingerprinting with your website.

  • Insert a script on the webpage/application where you want collect device fingerprinting information.

    <script src="https://fpt.<Your_Sub_Domain>.com/mdt.js?session_id=<session_id>&instanceId=<instance_id>" type="text/javascript"></script>
    • Your_Root_Domain – The root domain of the merchant website.
    • session_id – The unique session identifier of the device created by the merchant. It can be up to 128 characters long and can contain only the following characters: uppercase and lowercase Roman letters, digits, underscore characters, and hyphens (a–z, A–Z, 0–9, _, -). Although we recommend that you use a globally unique identifier (GUID) for the session ID, this approach isn't required.
    • instance_id – A placeholder for the instance ID that represents you. Use the instance identifier (instance_id value) listed on the Account Information dashboard tile in the Dynamics 365 Fraud Protection Evaluate experience. You must have this value to integrate device fingerprinting with your website.


    <script src="https://Your_Sub_Domain/mdt.js?session_id=211d403b-2e65-480c-a231-fd1626c2560e&instanceId=b472dbc3-0928-4577-a589-b80090117691" type="text/javascript"></script>

    Here is an example of a response for mdt.js.

    window.dfp={url:"https://Your_Sub_Domain/?session_id=211d403b-2e65-480c-a231-fd1626c2560e&CustomerId=b472dbc3-0928-4577-a589-b80090117691",sessionId:"211d403b-2e65-480c-a231-fd1626c2560e",customerId:"b472dbc3-0928-4577-a589-b80090117691",dc:"uswest"};window.dfp.doFpt=function(doc){var frm,src;true&&(frm=doc.createElement("IFRAME"),"fpt_frame","1px","1px","absolute","hidden","10px","0px",frm.setAttribute("style","color:#000000;float:left;visibility:hidden;position:absolute;top:-100;left:-200;border:0px"),src="https://Your_Sub_Domain/?session_id=211d403b-2e65-480c-a231-fd1626c2560e&CustomerId=b472dbc3-0928-4577-a589-b80090117691",frm.setAttribute("src",src),doc.body.appendChild(frm))};
  1. Load device fingerprinting after the page's elements are loaded.

  2. When you submit transactions in the Dynamics 365 Fraud Protection API, set a session ID in the deviceContextId field.

  3. Set the 'device.ipAddress' field to the customer IP address that your website receives when the customer uses your site.

Mobile device fingerprinting


You can learn more about the Mobile Reference Implementation in the DFP Mobile Reference Implementation Document. A login is required.