Merge pull request #49006 from MicrosoftDocs/NEW-priva-consent-management

New priva consent management

Author: v-dirichards

learn-pr/wwl-sci/priva-consent-management/consent-management-overview.yml

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

learn-pr/wwl-sci/priva-consent-management/consent-management-prerequisites.yml

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

learn-pr/wwl-sci/priva-consent-management/create-consent-model.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.priva-consent-management.create-consent-model
+title: Create consent models
+metadata:
+  title: Create consent models
+  description: "Create consent models"
+  ms.date: 01/24/2025
+  author: wwlpublish
+  ms.author: riswinto
+  ms.topic: unit
+azureSandbox: false
+labModal: false
+durationInMinutes: 9
+content: |
+  [!include[](includes/create-consent-model.md)]

learn-pr/wwl-sci/priva-consent-management/create-package-publish-profile.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.priva-consent-management.create-package-publish-profile
+title: Create and manage consent model packages
+metadata:
+  title: Create and manage consent model packages
+  description: "Create and manage consent model packages"
+  ms.date: 01/24/2025
+  author: wwlpublish
+  ms.author: riswinto
+  ms.topic: unit
+azureSandbox: false
+labModal: false
+durationInMinutes: 5
+content: |
+  [!include[](includes/create-package-publish-profile.md)]

learn-pr/wwl-sci/priva-consent-management/includes/consent-management-overview.md

@@ -0,0 +1,17 @@
+In today's digital age, most interactions with companies, websites, and apps involve the collection of personal data. This increase in data collection has made it essential for organizations to meet data privacy requirements and provide clear consent and notice around how personal data is collected and used.
+
+Microsoft Priva Consent Management (preview) offers a flexible, regulation-independent solution to manage consented personal data. By providing customizable consent models and a centralized process for publishing at scale, this tool ensures that data collection aligns with consent preferences and responsible data practices.
+
+## How it works
+
+**Microsoft Priva Consent Management** allows you to create two types of consent models—tracker consent models and generic consent models—through a guided process. For tracker consent models, categories help organize and manage different types of consent, providing a structured way to align tracking practices with user preferences. Consent models can be reused across public domains and don’t need to be tied to specific websites. You can customize layouts to match your organization’s branding and include language translations to support visitors across multiple regions.
+
+Once your consent models are ready, you can publish them globally using a centralized process. Deployment options include manually downloading packages, connecting to Azure Storage, or using content delivery networks (CDNs) such as Microsoft Azure, Amazon Web Services, and Cloudflare.
+
+Consent Management integrates with [**Microsoft Priva Tracker Scanning (Preview)**](/privacy/priva/tracker-scanning?azure-portal=true) to use website scan results for enabling or disabling tracker categories. This integration ensures user preferences are respected in real time.
+
+By streamlining consent management, Microsoft Priva helps organizations manage personal data effectively while meeting data privacy requirements. Next, learn how to set up consent models, configure tracker categories, and deploy them efficiently in your organization.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-consent-management/includes/consent-management-prerequisites.md

@@ -0,0 +1,54 @@
+Microsoft Priva Consent Management (preview) helps your organization create and manage consent models that are customizable and independent of specific regulations. This allows you to track consumer consent across your entire data estate. Once you've familiarized yourself with the benefits of Microsoft Priva Consent Management, the next step is to set up and manage your consent models. 
+
+## Process overview
+
+To effectively manage consent, follow these steps:
+
+1. **Set up your tracker consent models**:
+   - Create tracker categories to organize and manage different types of consent.
+   - Optionally, design a custom layout to match your branding.
+   - Add or import translations to support multiple languages.
+   - Mark the model as complete to prepare it for publishing.
+
+1. **Create a generic consent model**:
+   - Skip creating tracker categories.
+   - Complete the remaining steps as outlined for tracker consent models.
+
+1. **Generate and deploy a package**:
+   - Generate a package for your completed consent model.
+   - Configure publishing profiles and deploy using manual downloads, Azure Storage, or content delivery networks (CDNs).
+
+## How to access consent management
+
+To access consent management:
+
+1. Navigate to the **Microsoft Priva** portal.
+1. Select the **Consent Management** tile from the top row of solutions.
+1. If the tile isn't visible, select **View all solutions**, and under the **Privacy** heading, select **Consent Management**.
+
+## Roles and permissions
+
+Assigning the right roles to users in your organization is crucial for effective consent management:
+
+|Role|Description|
+|---|----------|
+|Privacy Curator |Create consent models<br>Create layouts<br>Generate packages<br>Configure publishing profiles<br>Read reports|
+|Privacy Reader |View consent models<br>View layouts<br>Read reports|
+
+For more information on roles and how to assign them, see [Data governance roles and permissions in Microsoft Purview](/purview/data-governance-roles-permissions?azure-portal=true).
+
+## Understand the consent management overview page
+
+The **Overview** page in consent management features a set of setup tasks designed to help users get started efficiently. Completed tasks remain listed on the page for two weeks with a **Completed** status next to their name.
+
+The **Create new** section lets you quickly start a consent model, layout, or publishing profile. These tasks can also be completed on the **Models and Layout** page and the **Packages and Publishing** page.
+
+:::image type="content" source="../media/consent-management-overview.png" alt-text="Screenshot showing the Consent Management Overview page." lightbox="../media/consent-management-overview.png":::
+
+## Create tracker categories
+
+You can automatically link consent models to the tracker categories you create in Priva tracker scanning or in consent management. Set up tracker categories in advance to automatically link them with consent models. For more information on creating a tracker category, see [Create tracker categories and manage trackers in tracker scanning (preview)](/privacy/priva/tracker-scanning-tracker-categories?azure-portal=true).
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-consent-management/includes/create-consent-model.md

@@ -0,0 +1,124 @@
+Microsoft Priva Consent Management (preview) allows your organization to build customizable, regulatory-independent consent models. These models can be deployed across multiple regions, supporting your compliance requirements without needing site-specific models.
+
+A consent model defines how an organization collects, manages, and stores user consent for data processing. It ensures users are informed about what data is collected and how it will be used. It also provides them with the option to agree or decline. Implementing a consent model helps organizations:
+
+- Adhere to data protection regulations
+- Build trust through transparency
+- Empower users to make informed choices
+- Reduce legal risks and potential reputational damage
+
+## Types of consent models
+
+Consent management supports two types of consent models:
+
+- **Tracker consent model**: Manages cookies and other tracking technologies. This model controls whether cookies are turned on or off based on user consent. It helps meet regulatory requirements that mandate explicit consent for tracking user behavior online.
+- **Generic consent model**: Handles other types of user consent not related to cookies. Organizations can use this model to manage consent for data processing activities that don't involve web tracking.
+
+Choosing the right model depends on how your organization collects and processes user data.
+
+## Implicit and explicit consent types
+
+When setting up consent models, you need to determine whether consent should be explicit or implicit:
+
+- **Explicit consent (opt-in)**: Requires users to affirmatively accept trackers. Nonessential trackers are off by default until the user explicitly grants permission.
+- **Implicit consent (opt-out)**: Assumes user consent by default. Nonessential trackers are on by default, and users must take action to opt out.
+
+**Explicit consent** is required in many jurisdictions with strict data protection laws, while **implicit consent** might be permitted in regions with less stringent regulations.
+
+## Models and layout page
+
+The **Models and layout** page is the central location for creating and managing consent models and layouts.
+
+### Consent models tab
+
+Displays all consent models, including details such as:
+
+- **Type**: Tracker or generic
+- **Consent type**: Explicit or implicit
+- **Status**: Draft, in progress, complete, published
+
+Selecting a model opens its details page, where you can edit, preview, manage translations, and view associated tracker categories.
+
+### Layouts tab
+
+Displays built-in and custom layouts that define the look and feel of the consent experience. You can edit, preview, and associate layouts with consent models.
+
+### Tracker categories tab
+
+Lists tracker categories that help organize different types of trackers. Categories can be created in Priva Tracker Scanning or directly in Consent Management.
+
+## Built-in layouts in consent management
+
+Consent models use layouts to determine how consent experiences appear on a website. Consent management includes built-in system layouts that define how users interact with consent banners, preferences, and pop-ups.
+
+:::image type="content" source="../media/built-in-layout.png" alt-text="Screenshot of built-in consent management layouts, including Preference Layout, Banner Layout, Footer Link Layout, and Single Page Layout." lightbox="../media/built-in-layout.png":::
+
+- **Preference Layout**: Allows users to modify tracker category selections.
+- **Banner Layout**: Displays a consent banner with a hyperlink to a second page.
+- **Footer Link Layout**: Shows a footer banner with a hyperlink to a second page.
+- **Single Page Layout**: Uses a floating pop-up with Accept or Decline options.
+
+When setting up a consent model, you can select one of these layouts. If none of these meet your needs, you can create a custom layout.
+
+## Create a custom layout
+
+Custom layouts allow you to personalize the consent experience to align with your organization's branding and website design. While built-in layouts are available, custom layouts provide a higher level of control and flexibility.
+
+**Steps to create a layout**:
+
+1. Go to the **Models and layout** page.
+1. Select the **Layouts** tab, then **New layout**.
+1. Enter the **Name**, **Description**, and **Contacts** for the layout.
+1. Choose a layout template and customize it.
+1. Add components and pages as needed.
+1. Save the layout and mark it as complete.
+
+Once a layout is marked complete, it becomes available for use in consent models.
+
+### Create a tracker consent model
+
+To create a tracker consent model:
+
+1. Go to the **Models and layout** page.
+1. Select **New consent model** and choose **Tracker consent**.
+1. Enter the name, description, owner, target regions, and default language.
+1. Select a layout and preview its design.
+1. Add banner and preferences text to communicate consent options clearly.
+1. Customize the model's appearance and style settings.
+1. Preview, save, and close the model.
+
+Once created, the consent model appears in the **Consent models** tab, where you can add translations and manage its settings.
+
+## Add translations
+
+Translations ensure your consent model is accessible to users in different languages. You can add translations using:
+
+- **Manual translation**: Add translations individually for each language.
+- **Import translations**: Use a downloadable template to import multiple translations.
+- **Auto translation**: Generate machine-based translations for selected languages.
+
+## Preview the consent model
+
+Before deploying a consent model, preview it to verify its content and design:
+
+- **Live preview**: Shows how the model will appear on your website.
+- **Mockup preview**: Displays a simple version of the model with translation options.
+
+## Mark as complete
+
+Once you've configured the layout, content, and translations, review all settings. When the model is finalized, select Mark as complete.
+
+A **completed** consent model can be added to a deployment package for use on websites.
+
+## Version history
+
+Consent models retain a version history, allowing you to:
+
+- Access the last **two versions** of a consent model.
+- Restore or promote a previous version if needed.
+
+After marking a consent model as complete, create a package to **publish and deploy** it on your website.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-consent-management/includes/create-package-publish-profile.md

@@ -0,0 +1,73 @@
+Before deploying a consent model, organizations need a way to group multiple models together for efficient management. A consent model package serves as the container that holds one or more consent models, ensuring they apply correctly across different websites and endpoints.
+
+By creating a **consent model package**, you can:
+
+- **Standardize** how consent models are deployed across multiple sites.
+- **Group explicit** and implicit consent models based on regulatory needs.
+- **Streamline management** by applying changes to multiple models at once.
+
+## Create a consent model package
+
+A consent model package ensures that models are deployed consistently across all necessary locations. Follow these steps to create one:
+
+1. Navigate to the **Packages and publishing** page in consent management and select the Packages tab.
+1. Select **New package**.
+1. On the **Basic details** page, enter a **Package name**, a **Description**, and select a **Consent model type**:
+
+   - **Tracker consent**: Optionally, enable tracker blocking and unknown tag blocking.
+   - **Generic consent**: Group models together and enable consent sharing if needed.
+
+1. Select one or more consent models to include in the package and select **Next**.
+1. Choose a fallback consent model for unknown visitor conditions on the **Default consent model** page.
+1. Select **Create** to finish setting up the package.
+
+Once created, the package appears in the Packages tab. The status updates from Active to Complete when the configuration file is ready.
+
+## Edit an existing consent model package
+
+After creating a package, you might need to update it. Editing a package allows you to add or remove consent models as your organization's needs change.
+
+To edit a package:
+
+1. Go to the **Packages and publishing** page.
+1. Select the **Packages** tab and choose the package you want to edit.
+1. Select **Edit**, make the necessary changes, and save.
+
+When a package is modified, the system regenerates the configuration file to reflect the updates.
+
+## Create a publishing profile
+
+A **publishing profile** connects different websites to consent models, ensuring that the correct models apply based on visitor conditions. There are two types of publishing profiles:
+
+- **Storage profile**: Uses an Azure Storage account to store and distribute consent configurations.
+- **CDN profile**: Uses a Content Delivery Network (CDN) like Azure or Cloudflare to distribute consent models to websites.
+
+### Create a storage profile
+
+1. On the **Packages and publishing** page, select the **Profiles** tab and select **New profile**.
+1. Choose **Storage** and select **Next**.
+1. Enter the **Profile Name**, **Description**, and **Contact details**.
+1. Select **Azure** as the provider and enter the **Client Credential** name and **Azure Storage subpath**.
+1. Select **Save and close**.
+
+### Create a CDN profile
+
+1. On the **Packages and publishing** page, select the **Profiles** tab and select **New profile**.
+1. Choose **CDN** and select **Next**.
+1. Enter the **Profile Name**, **Description**, and **Contact details**.
+1. Select **Azure** or **Cloudflare** as the provider.
+1. Enter the **Public endpoint URL** and **Purge URL**.
+1. Associate websites and packages with the profile and select **Save and close**.
+
+## Publish and manage profiles
+
+Once a profile is created and its status is Complete, you can:
+
+1. Generate a deployment snippet to apply it to a website.
+1. Publish the profile to a CDN for wider distribution.
+
+This ensures that consent models are deployed consistently across multiple websites and that updates are automatically applied when consent models change.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)

learn-pr/wwl-sci/priva-consent-management/includes/introduction.md

@@ -0,0 +1,23 @@
+Digital interactions often involve sharing personal data, whether it’s creating accounts, making purchases, or signing up for services. While this data helps improve personalization and enhance user experiences, it can lead to privacy concerns if users don’t understand how their information is being collected, stored, or shared. For organizations, managing these concerns is essential to maintaining trust and ensuring transparency.
+
+Microsoft Priva Consent Management (preview) helps organizations track and manage user consent preferences efficiently. By using this tool, organizations can align their practices with privacy regulations, honor user expectations, and promote responsible data practices.
+
+## Scenario
+
+Your organization is expanding digital services into new regions. Feedback shows users are confused about how their personal data is handled, and your team is struggling to centralize and manage consent preferences across platforms. Without a reliable system to track and honor consent, the organization risks losing user trust and failing to meet privacy standards.
+
+You need a solution to simplify consent management, ensure compliance, and build transparency into your data practices.
+
+## Learning objectives
+
+By the end of this module, you'll be able to:
+
+- Describe the purpose and benefits of Microsoft Priva Consent Management.
+- Set up consent models and configure prerequisites like tracker categories.
+- Create and apply publishing profiles to manage consent models.
+- Deploy consent models across websites using consent model packages.
+- Ensure consent models remain accurate and aligned with privacy requirements.
+
+## Legal disclaimer
+
+[Microsoft Priva legal disclaimer](/privacy/priva/priva-disclaimer?azure-portal=true)