Merge pull request #49004 from riswinto/NEW-priva-tracker-scanning

New priva tracker scanning

Author: JillGrant615

learn-pr/wwl-sci/priva-tracker-scanning/configure-tracker-scanning.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.priva-tracker-scanning.configure-tracker-scanning
+title: Configure tracker scanning
+metadata:
+  title: Configure tracker scanning
+  description: "Configure tracker scanning"
+  ms.date: 01/24/2025
+  author: wwlpublish
+  ms.author: riswinto
+  ms.topic: unit
+azureSandbox: false
+labModal: false
+durationInMinutes: 5
+content: |
+  [!include[](includes/configure-tracker-scanning.md)]

learn-pr/wwl-sci/priva-tracker-scanning/create-manage-trackers.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.priva-tracker-scanning.create-manage-trackers
+title: Create and manage trackers and tracker categories
+metadata:
+  title: Create and manage trackers and tracker categories
+  description: "Create and manage trackers and tracker categories"
+  ms.date: 01/24/2025
+  author: wwlpublish
+  ms.author: riswinto
+  ms.topic: unit
+azureSandbox: false
+labModal: false
+durationInMinutes: 10
+content: |
+  [!include[](includes/create-manage-trackers.md)]

learn-pr/wwl-sci/priva-tracker-scanning/includes/configure-tracker-scanning.md

@@ -0,0 +1,55 @@
+Configuring the environment and assigning appropriate roles are essential steps before using Microsoft Priva Tracker Scanning (preview). These steps ensure that tracking technologies can be identified, categorized, and managed effectively across your organization's websites, enabling transparency and alignment with privacy practices.
+
+> [!IMPORTANT]
+> To use Microsoft Priva Tracker Scanning (preview), your organization must have the enterprise version of Microsoft Purview data governance solutions. This version provides access to the necessary tools and features required for effective tracker scanning. For more information on upgrading, see [Upgrade from the free to enterprise version of Microsoft Purview governance solutions](/purview/upgrade?azure-portal=true).
+
+## Prerequisites
+
+Before configuring Microsoft Priva Tracker Scanning, ensure that your organization meets the following requirements:
+
+### Roles and permissions
+
+Proper role assignment is essential for users to perform tasks in Tracker Scanning. The following roles define the permissions available:
+
+| Role | Permissions |
+|-----|-----|
+| **Data Source Administrator** | Register, edit, and update websites. |
+| **Privacy Curator** | View and edit all privacy objects, create and categorize trackers, promote trackers, and view tags. |
+| **Privacy Reader** | Review scan results, view the tracker library, and access identified trackers without making edits. |
+
+For more information, see [Data governance roles and permissions in Microsoft Purview](/purview/data-governance-roles-permissions?azure-portal=true).
+
+### Access tracker scanning
+
+Tracker Scanning is located in the Microsoft Priva portal. Follow these steps to access it:
+
+1. Navigate to the [Microsoft Priva portal](https://purview.microsoft.com/priva?azure-portal=true).
+1. Select the **Tracker Scanning** tile from the top row of solutions.
+1. If the **Tracker Scanning** tile isn't visible, select **View all solutions**, and under the **Privacy** heading, select **Tracker Scanning**.
+
+## Register websites
+
+Once the prerequisites are met, the next step is to register your organization's websites in Tracker Scanning. Registration connects websites to Tracker Scanning, allowing you to monitor and manage trackers effectively.
+
+The **Registered websites** page is where you manage all sites added to Tracker Scanning. Each registered site includes key details, such as its URL, owner, description, and the region where the website's domain is hosted. Selecting a website opens its details page, where you can create and manage scans, review identified trackers, and organize them into categories. The details page also allows you to view associated [consent models](/privacy/priva/consent-management-create?azure-portal=true) for the registered website.
+
+Registering a website ensures that tracker scanning can identify tracking technologies, detect potential compliance issues (like missing consent banners), and provide insights for improving privacy practices. This step is typically completed by someone familiar with the website's domain and scanning requirements.
+
+To register a website:
+
+1. Navigate to the **Registered websites** page and select **Register**.
+1. Enter the following details:
+   - **Name and description**: Provide a meaningful name and description for the website.
+   - **Website URL**: Add the URL of the website to scan.
+   - **Regulatory country or region**: Select the location where the website is hosted.
+   - **Owner**: Specify the name or email of the user responsible for the site.
+   - **Business domain**: Use the [default domain](/purview/concept-domains?azure-portal=true) for setting up websites and scans.
+   - **Collection**: Choose the collection that the website should belong to. Collections help group related websites, making it easier to organize and manage them within Tracker Scanning. For more information, see [Manage domains and collections in the Microsoft Purview Data Map](/purview/how-to-create-and-manage-domains-collections?azure-portal=true).
+
+1. Select **Create** to complete the process.
+
+After registration, websites appear on the **Registered websites** page. From there, you can manage scans, view tracker details, and organize trackers into categories to align with your organization's privacy goals.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-tracker-scanning/includes/create-manage-trackers.md

@@ -0,0 +1,102 @@
+Trackers and tracker categories are essential components of Microsoft Priva Tracker Scanning. They enable your organization to identify and organize tracking technologies across websites, ensuring better compliance with privacy practices and supporting user consent preferences. Tracker categories also integrate with [Microsoft Priva Consent Management (preview)](/privacy/priva/consent-management?azure-portal=true) to ensure only consented trackers are active, helping organizations build trust and comply with privacy standards.
+
+## Tracker management overview
+
+The **Tracker management** page in tracker scanning is your central hub for managing and categorizing trackers. It's divided into the following sections:
+
+- **Trackers tab**: Displays all trackers identified through scans or added manually. You can edit tracker properties, assign categories, and view details about each tracker.
+- **Tracker categories tab**: Allows you to create, view, and manage tracker categories, including translations.
+- **Common tracker database tab**: Serves as a reference inventory of widely used non-Microsoft trackers, which can be mapped to your organization's tracker categories.
+- **Tracker library**: A curated list of approved trackers used across your organization for proactive compliance.
+
+:::image type="content" source="../media/tracker-management.png" alt-text="Screenshot showing the menu for the tracker management options in Tracker Scanning." lightbox="../media/tracker-management.png":::
+
+Each tracker or tracker category includes detailed information, such as its name, description, owner, and associated websites.
+
+### Create tracker categories
+
+Tracker categories help group trackers based on their purpose, such as advertising, analytics, or functional tasks. Setting up categories ensures that trackers are organized and ready for use in consent models.
+
+To create a tracker category:
+
+1. Navigate to the **Tracker management** page and select the **Tracker categories** tab.
+1. Select **New tracker category**.
+1. Provide the following details in the **Add tracker category** flyout pane:
+   - **Category name**: Enter a public-facing name for the category (for example, Advertising, Functional). This name appears in consent banners.
+   - **Use guidelines**: Add internal-facing guidance about the appropriate use of trackers in this category.
+   - **Owner**: Assign a user responsible for managing the category.
+   - **Essential status**: Check the **Essential** box if trackers in this category must always deploy, regardless of user consent.
+1. Select **Save** to create the category.
+
+Categories marked as **Essential** deploy by default, while nonessential categories require user consent to be activated. You can also add translations to tracker categories to support multilingual environments.
+
+#### Add translations to categories
+
+Language translations ensure that tracker categories are accessible to users in multiple regions. To add a translation:
+
+1. On the **Tracker management** page, go to the **Tracker categories** tab and select a tracker category.
+1. Select **New translation** and choose an option:
+   - **Manual translation**
+   - **Import translations**
+   - **Auto translation**
+1. Follow the process to add translations for each language needed.
+
+### Categorize trackers
+
+Categorizing trackers is a critical step for enabling consent model interactions in Microsoft Priva Consent Management. Proper categorization ensures that when users interact with consent banners or privacy settings, only trackers that have been consented to remain active. This step also supports building a complete inventory of tracking technologies used on your websites.
+
+To categorize a tracker:
+
+1. Navigate to the **Trackers** tab on the **Tracker management** page.
+1. Select a tracker from the list to open its details page.
+1. On the tracker's details page, select **Categorize**.
+1. In the **Categorize** flyout pane, choose a category and select **Apply**.
+
+Once categorized, the tracker's category is reflected in all future scans. Each tracker can only be assigned to one category at a time.
+
+### Manually add trackers
+
+Some trackers might not be detected during scans and need to be added manually. This ensures all relevant trackers are included in your inventory.
+
+To add a tracker manually:
+
+1. On the **Trackers** tab of the **Tracker management** page, select **New tracker**.
+1. Provide the following details:
+   - **Basic details**: Enter the tracker's name, description, and the domain of the website using the tracker.
+   - **Owner**: Assign a user responsible for the tracker.
+   - **Tracker category**: Select the category to which the tracker belongs.
+1. Select **Save** to add the tracker.
+
+The tracker is added to your list and can be managed like other trackers detected through scans.
+
+### Manage the tracker library
+
+The **Tracker library** is a curated list of approved trackers used across your organization. It supports proactive compliance by ensuring that web engineers use preapproved trackers instead of open-source or unapproved options.
+
+To promote a tracker to the library:
+
+1. Navigate to the **Tracker library** page and select **Manage promoted trackers**.
+1. Use the **Your trackers** tab to find trackers discovered through scans or added manually. Alternatively, use the **Common trackers** tab to select trackers from the common tracker database.
+1. Select the trackers to promote, then select **Add**.
+
+Promoted trackers appear in the library but can be removed without being deleted from the system.
+
+### Common tracker database
+
+The **Common tracker database** is a reference list of non-Microsoft trackers commonly used on websites. While these trackers aren't initially categorized with your organization's tracker categories, they can be mapped as needed.
+
+:::image type="content" source="../media/common-tracker-database.png" alt-text="Screenshot showing common tracker database in tracker management." lightbox="../media/common-tracker-database.png":::
+
+To map common trackers to your organization's categories:
+
+1. On the **Common tracker database** tab, select **Map categories**.
+1. In the **Map tracker categories** flyout pane, use the dropdown menu to map each default category (denoted as **System**) to a category created by your organization.
+1. Select **Save** to apply the changes.
+
+The **User-defined category** column now reflects the mapped categories, ensuring consistency across your tracker inventory.
+
+Once your trackers and tracker categories are created and organized, the next step is to use Microsoft Priva Tracker Scanning to identify and analyze tracking technologies across your registered websites. Running scans enables you to detect trackers in action, validate compliance elements like consent banners, and ensure your tracking practices align with privacy expectations. Let’s explore how to configure and run scans to monitor and manage web trackers effectively.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-tracker-scanning/includes/introduction.md

@@ -0,0 +1,23 @@
+Web trackers like cookies, device fingerprinting, and web beacons play a critical role in delivering personalization, analytics, and advertising. However, they can raise privacy concerns when users don't know they're being tracked or can't control how their data is used. Organizations must address these concerns while maintaining transparency and trust with their users.
+
+Microsoft Priva Tracker Scanning helps organizations automatically detect, categorize, and manage tracking technologies on their websites. With this tool, you can create a complete inventory of trackers, understand their purpose, and ensure they're used responsibly. Tracker Scanning enables organizations to maintain visibility into their web tracking practices and better align with user expectations, fostering responsible data practices.
+
+## Scenario
+
+Your organization, a global e-commerce company, expanded to new regions. Customers are raising concerns about website tracking, and gaps in your tracking practices have been identified. Without visibility into the trackers deployed across your websites, addressing these challenges has been difficult, leaving your organization at risk.
+
+You need a solution to automatically identify and categorize web trackers, ensuring that they're used responsibly and in alignment with user expectations.
+
+## Learning objectives
+
+By the end of this module, you'll be able to:
+
+- Explain the purpose and benefits of Microsoft Priva Tracker Scanning.
+- Configure Tracker Scanning and set up prerequisites.
+- Manage tracker categories and assign trackers effectively.
+- Run scans to detect tracking technologies and compliance issues.
+- Analyze scan results to support privacy compliance and optimize tracking practices.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-tracker-scanning/includes/run-a-scan.md

@@ -0,0 +1,64 @@
+Running scans in Microsoft Priva Tracker Scanning allows your organization to identify and analyze tracking technologies across registered websites. These scans help ensure compliance with privacy practices by detecting tracking technologies such as cookies, fingerprints, local storage objects, and web beacons. With customizable options, you can configure scans to meet your organization's specific requirements.
+
+## Setting up a scan
+
+Before running a scan, ensure that the website is registered and tracker categories are configured. Once these prerequisites are complete, follow these steps to configure a scan:
+
+1. Navigate to the **Registered websites** page and select the website you wish to scan.
+1. On the website's details page, select **New compliance scan**.
+1. In the **Scan** flyout pane, provide the following details:
+   - **Compliance scan name**: Enter a unique name for the scan. This name can't be changed after creation.
+   - **Description**: Add a brief description of the scan's purpose.
+   - **Scan region**: Select the region where the scan will be performed, such as East US, UK South, or West Europe. This option simulates how the website operates under the privacy requirements of the chosen region.
+   - **Crawl definition**: Select one of the following options for the scan:
+     - **Registered URL only**: Scans only the first page of the registered domain.
+     - **Crawl (registered URL + two levels)**: Scans the registered domain and up to two levels of pages linked within the domain.
+     - **Sitemap**: If your website has a sitemap, provide its URL. This option scans all pages identified in the sitemap (up to 3 MB in size).
+   - **Limit scan to**: Define the maximum number of pages to scan. Increasing this limit can result in longer scan times and varying costs.
+
+1. Select **Continue** to move forward with configuring more scan options.
+
+## Configuring tracker technologies and compliance objects
+
+In this step, define what the scan should detect:
+
+:::image type="content" source="../media/run-tracker-scanner.png" alt-text="Screenshot showing the trackers and tags for tracker scanner to detect." lightbox="../media/run-tracker-scanner.png":::
+
+- **Tracker technologies**: Select the types of trackers to scan for. Options include:
+  - **Cookies**: First- and third-party cookies deployed when a webpage loads.
+  - **Fingerprints**: Device and browser fingerprints used for configurations or profiling.
+  - **Local storage**: Local storage objects stored on a visitor's device.
+  - **Web beacons**: Invisible images or scripts used for tracking user behavior.
+- **Tags and relationships**: Choose whether to capture associated tags and relationships for the selected trackers. This option helps map relationships between trackers and their deployment.
+
+- **Compliance objects**: Select compliance elements to verify their presence on the website. Common compliance objects include:
+  - **Consent banners**
+  - **Privacy statements**
+
+To add a compliance object, enter its location path manually or use the Microsoft Edge extension to generate and upload a JSON file. For more information, see [Collecting location paths](/privacy/priva/location-paths?azure-portal=true).
+
+## Scheduling scans
+
+You can set up scans to run either as a one-time event or on a recurring schedule. To schedule scans:
+
+1. On the **Set a scan trigger** page, choose a frequency:
+   - **Once**: Run the scan immediately after setup.
+   - **Recurring**: Schedule the scan to run daily, weekly, or monthly. Specify start and end dates, and select specific days for weekly or monthly scans.
+2. Select **Continue** to finalize the schedule.
+
+## Reviewing and initiating scans
+
+Before running the scan, review the scan settings on the **Review your scan** page:
+
+1. Verify all configurations, including the scan name, region, tracker technologies, and compliance objects.
+1. Select one of the following options:
+   - **Save**: Save the scan without running it.
+   - **Save and run**: Save the scan and initiate it immediately.
+
+Once the scan is complete, results are available on the **Scan results** page, where you can analyze detected trackers, review compliance objects, and address potential issues.
+
+Running scans in Microsoft Priva Tracker Scanning is a critical step for maintaining compliance with privacy regulations and ensuring transparency in your organization's tracking practices. By using features like regional scanning, customizable tracker detection, and recurring schedules, you can proactively manage compliance and support responsible data practices.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)