Merge pull request #12395 from MicrosoftDocs/main

9/26/2024 PM Publish

.openpublishing.redirection.json

@@ -5037,7 +5037,7 @@
         },   
         {
             "source_path": "powerbi-docs/admin/service-security-dlp-policies-for-power-bi.md",
-            "redirect_url": "/power-bi/enterprise/service-security-dlp-policies-for-power-bi",
+            "redirect_url": "/fabric/governance/data-loss-prevention-overview",
             "redirect_document_id": false
         }, 
         {
@@ -5443,13 +5443,28 @@
         },
         {
             "source_path": "powerbi-docs/enterprise/service-security-dlp-policies-for-power-bi.md",
-            "redirect_url": "/power-bi/enterprise/service-security-dlp-policies-for-power-bi-overview",
-            "redirect_document_id": true
+            "redirect_url": "/fabric/governance/data-loss-prevention-overview",
+            "redirect_document_id": false
         },
         {
             "source_path": "powerbi-docs/enterprise/service-security-dlp-policies-for-power-bi-override.md",
-            "redirect_url": "/power-bi/enterprise/service-security-dlp-policies-for-power-bi-respond",
-            "redirect_document_id": true
+            "redirect_url": "/fabric/governance/data-loss-prevention-respond",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "powerbi-docs/enterprise/service-security-dlp-policies-for-power-bi-overview.md",
+            "redirect_url": "/fabric/governance/data-loss-prevention-overview",
+            "redirect_document_id": false
+        },
+		{
+            "source_path": "powerbi-docs/enterprise/service-security-dlp-policies-for-power-bi-configure.md",
+            "redirect_url": "/fabric/governance/data-loss-prevention-configure",
+            "redirect_document_id": false
+        },
+		{
+            "source_path": "powerbi-docs/enterprise/service-security-dlp-policies-for-power-bi-respond.md",
+            "redirect_url": "/fabric/governance/data-loss-prevention-respond",
+            "redirect_document_id": false
         },
         {
             "source_path": "powerbi-docs/transform-model/log-analytics/install-as-engine-app.md",

powerbi-docs/connect-data/service-gateway-enterprise-manage-ssas.md

@@ -7,18 +7,19 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: powerbi-gateways
 ms.topic: how-to
-ms.date: 02/15/2023
+ms.date: 09/23/2024
 ms.custom: video-removed, video-removed
 LocalizationGroup: Gateways
+#customer intent: As a Power BI user I want to learn how to manage SQL Server Analysis services for the on-premisis gateway.
 ---
 # Manage SQL Server Analysis Services data sources
 
-[!INCLUDE [gateway-rewrite](../includes/gateway-rewrite.md)]
-
 After you [install an on-premises data gateway](/data-integration/gateway/service-gateway-install), you can [add data sources](service-gateway-data-sources.md#add-a-data-source) to use with the gateway. This article describes how to add a SQL Server Analysis Services (SSAS) data source to your on-premises gateway to use for scheduled refresh or for live connections.
 
 To learn more about how to set up a live connection to SSAS, watch this [Power BI Walkthrough: Analysis Services Live Connect](https://www.youtube.com/watch?v=GPf0YS-Xbyo&feature=youtu.be) video.
 
+[!INCLUDE [gateway-rewrite](../includes/gateway-rewrite.md)]
+
 > [!NOTE]
 > If you have an Analysis Services data source, you need to install the gateway on a computer joined to the same forest or domain as your Analysis Services server.
 
@@ -89,10 +90,6 @@ To do manual UPN mapping, follow these steps:
 
    :::image type="content" source="media/service-gateway-enterprise-manage-ssas/add-new-rules.png" alt-text="Screenshot of Add new rule in the Map user names box.":::
 
-   For example:
-
-   :::image type="content" source="media/service-gateway-enterprise-manage-ssas/replace-with-rule.png" alt-text="Screenshot of example mapping rules." :::
-
    > [!NOTE]
    > Be sure not to change users that you don't intend to change. For example, if you replace the **Original name** of `contoso.com` with a **New name** of `@contoso.local`, all user sign-ins that contain `@contoso.com` are replaced with `@contoso.local`. Also, if you replace an **Original name** of `[email protected]` with a **New name** of `[email protected]`, a sign-in of `[email protected]` is sent as `[email protected]`.
 

powerbi-docs/connect-data/service-gateway-sso-kerberos-sap-bw-commoncryptolib.md

@@ -30,15 +30,15 @@ This article describes how to configure your SAP BW data source to enable SSO fr
 
    For more information on setup steps, see [SAP Single Sign-On: Authenticate with Kerberos/SPNEGO](https://blogs.sap.com/2017/07/27/sap-single-sign-on-authenticate-with-kerberosspnego/). Your BW server should use CommonCryptoLib as its SNC Library and have an SNC name that starts with *CN=*, such as *CN=BW1*. For more information on SNC name requirements (specifically, the snc/identity/as parameter), see [SNC Parameters for Kerberos Configuration](https://help.sap.com/viewer/df185fd53bb645b1bd99284ee4e4a750/3.0/360534094511490d91b9589d20abb49a.html).
 
-1. If you haven't already done so, install the x64-version of the [SAP .NET Connector](https://support.sap.com/en/product/connectors/msnet.html) on the computer the gateway has been installed on. 
-   
+1. If you haven't already done so, install the x64-version of the [SAP .NET Connector](https://support.sap.com/en/product/connectors/msnet.html) on the computer the gateway has been installed on.
+
    You can check whether the component has been installed by attempting to connect to your BW server in  Power BI Desktop from the gateway computer. If you can't connect by using the 2.0 implementation, the .NET Connector isn't installed or hasn't been installed to the GAC.
 
-1. Ensure that SAP Secure Login Client (SLC) isn't running on the computer the gateway is installed on. 
+1. Ensure that SAP Secure Login Client (SLC) isn't running on the computer the gateway is installed on.
 
-   SLC caches Kerberos tickets in a way that can interfere with the gateway's ability to use Kerberos for SSO. 
+   SLC caches Kerberos tickets in a way that can interfere with the gateway's ability to use Kerberos for SSO.
 
-1. If SLC is installed, uninstall it or make sure you exit SAP Secure Login Client. Right-click the icon in the system tray and select **Log Out** and **Exit** before you attempt an SSO connection by using the gateway. 
+1. If SLC is installed, uninstall it or make sure you exit SAP Secure Login Client. Right-click the icon in the system tray and select **Log Out** and **Exit** before you attempt an SSO connection by using the gateway.
 
    SLC isn't supported for use on Windows Server machines. For more information, see [SAP Note 2780475](https://launchpad.support.sap.com/#/notes/2780475) (s-user required).
 
@@ -65,11 +65,11 @@ This article describes how to configure your SAP BW data source to enable SSO fr
     - Choose **SAP Business Warehouse** as the **Data Source Type** if you want to create an SSO connection to a BW Application Server. 
     - Select **Sap Business Warehouse Message Server** if you want to create an SSO connection to a BW Message Server.
 
-1. For **SNC Library**, select either the **SNC\_LIB** or **SNC\_LIB\_64** environment variable, or **Custom**. 
+1. For **SNC Library**, select either the **SNC\_LIB** or **SNC\_LIB\_64** environment variable, or **Custom**.
 
    - If you select **SNC\_LIB**, you must set the value of the **SNC\_LIB\_64** environment variable on the gateway machine to the absolute path of the 64-bit copy of sapcrypto.dll on the gateway machine. For example, *C:\Users\Test\Desktop\sapcrypto.dll*.
 
-   - If you choose **Custom**, paste the absolute path to *sapcrypto.dll* into the Custom SNC Library Path field that appears on the **Manage gateways** page. 
+   - If you choose **Custom**, paste the absolute path to *sapcrypto.dll* into the Custom SNC Library Path field that appears on the **Manage gateways** page.
 
 1. For **SNC Partner Name**, enter the SNC Name of the BW server. Under **Advanced settings**, ensure that **Use SSO via Kerberos for DirectQuery queries** is checked. Fill in the other fields as if you were establishing a Windows Authentication connection from PBI Desktop.
 
@@ -99,7 +99,7 @@ If you're unable to refresh the report in the Power BI service, you can use gate
 
 ### CPIC tracing
 
-1. To enable CPIC tracing, set two environment variables: **CPIC\_TRACE** and **CPIC\_TRACE\_DIR**. 
+1. To enable CPIC tracing, set two environment variables: **CPIC\_TRACE** and **CPIC\_TRACE\_DIR**.
 
    The first variable sets the trace level and the second variable sets the trace file directory. The directory must be a location that  members of the Authenticated Users group can write to. 
  
@@ -160,7 +160,7 @@ If you're unable to refresh the report in the Power BI service, you can use gate
     ccl/trace/directory=<drive>:\logs\sectrace
     ```
 
-2. Change the `ccl/trace/directory` option to a location to which members of the Authenticated Users group can write. 
+2. Change the `ccl/trace/directory` option to a location to which members of the Authenticated Users group can write.
 
 3. Alternatively, create a new .ini file to change this behavior. In the same directory as sapcrypto.ini and sapcrypto.dll, create a file named sectrace.ini, with the following content. Replace the `DIRECTORY` option with a location on your machine that members of the Authenticated Users group can write to:
 
@@ -175,8 +175,7 @@ If you're unable to refresh the report in the Power BI service, you can use gate
 
     For more information on CommonCryptoLib tracing, see [SAP Note 2491573](https://launchpad.support.sap.com/#/notes/2491573) (SAP s-user required).
 
-
-### Impersonation 
+### Impersonation
 
 This section describes troubleshooting symptoms and resolution steps for impersonation issues.
 
@@ -186,7 +185,7 @@ This section describes troubleshooting symptoms and resolution steps for imperso
 
 **Validation**: Refresh or create the report and collect the *GatewayInfo[date].log*. Open the latest GatewayInfo log file and check again the following string: **About to impersonate user DOMAIN\User (IsAuthenticated: True, ImpersonationLevel: Impersonation)** to ensure that the value for **ImpersonationLevel** matches **Impersonation**.
 
-### Delegation 
+### Delegation
 
 Delegation issues usually appear in the Power BI service as generic errors. To determine whether delegation is the issue, it's useful to collect the Wireshark traces and use *Kerberos* as a filter. For Kerberos errors reference, consult the [blog post](/archive/blogs/askds/kerberos-errors-in-network-captures). The rest of this section describes troubleshooting symptoms and resolution steps for delegation issues.
 

powerbi-docs/connect-data/service-gateway-sso-kerberos-sap-hana.md

@@ -7,17 +7,18 @@ ms.reviewer: ''
 ms.service: powerbi
 ms.subservice: powerbi-gateways
 ms.topic: how-to
-ms.date: 02/03/2023
+ms.date: 09/23/2024
 LocalizationGroup: Gateways
+#customer intent: As a Power BI user I want to learn how to configure SSO for my SAP HANA server using Power BI.
 ---
 
 # Use Kerberos for SSO to SAP HANA
 
+This article describes how to configure your SAP HANA data source to enable single sign-on (SSO) from the Power BI service.
+
 > [!IMPORTANT]
 > Because [SAP no longer supports OpenSSL](https://help.sap.com/viewer/b3ee5778bc2e4a089d3299b82ec762a7/2.0.05/en-US/de15ffb1bb5710148386ffdfd857482a.html), Microsoft has also discontinued its support. Your existing connections continue to work but you can no longer create new connections. Use SAP Cryptographic Library (CommonCryptoLib), or sapcrypto, instead.
 
-This article describes how to configure your SAP HANA data source to enable single sign-on (SSO) from the Power BI service.
-
 > [!NOTE]
 > Before you attempt to refresh a SAP HANA-based report that uses Kerberos SSO, complete the steps in both this article and [Configure Kerberos SSO](service-gateway-sso-kerberos.md).
 
@@ -159,7 +160,7 @@ Following the preceding steps should resolve the issue. If you still experience
 
 If you experience credentials errors, errors in the logs or traces expose errors that describe `Credentials are invalid` or similar errors. These errors might manifest differently on the data source side of the connection, such as SAP HANA. The following image shows an example error:
 
-:::image type="content" source="media/service-gateway-sso-kerberos-sap-hana/sap-hana-kerberos-troubleshooting-09.png" alt-text="Screenshot showing an invalid credentials error." lightbox="media/service-gateway-sso-kerberos-sap-hana/sap-hana-kerberos-troubleshooting-09.png" :::
+:::image type="content" source="media/service-gateway-sso-kerberos-sap-hana/sap-hana-kerberos-troubleshooting-092.png" alt-text="Screenshot showing an invalid credentials error." lightbox="media/service-gateway-sso-kerberos-sap-hana/sap-hana-kerberos-troubleshooting-092.png" :::
 
 #### Symptom 1
 

powerbi-docs/enterprise/TOC.yml

@@ -115,11 +115,11 @@
       expanded: false
       items:              
       - name: Overview of DLP policies for Power BI
-        href: service-security-dlp-policies-for-power-bi-overview.md
+        href: /fabric/governance/data-loss-prevention-overview
       - name: Configure a DLP policy for Power BI
-        href: service-security-dlp-policies-for-power-bi-configure.md
+        href: /fabric/governance/data-loss-prevention-configure
       - name: Respond to a DLP policy violation
-        href: service-security-dlp-policies-for-power-bi-respond.md
+        href: /fabric/governance/data-loss-prevention-respond
   - name: Security
     expanded: false
     items:

powerbi-docs/enterprise/service-govus-overview.md

@@ -141,7 +141,7 @@ If a release is planned for an environment, we include the quarter of estimated
 |[Azure B2B collaboration between government and commercial cloud](service-admin-azure-ad-b2b.md)<sup>1</sup>|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png)
 |[Template apps](../connect-data/service-template-apps-overview.md)<sup>2</sup>|![Image of "Available" button.](../media/yes.png) |![Image of "Available" button.](../media/yes.png)| ![Image of "Available" button.](../media/yes.png)|
 |[Embed in SharePoint Online by using the Power BI web part](/sharepoint/dev/spfx/web-parts/overview-client-side-web-parts)|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png)|
-|[Data Loss Prevention policies](./service-security-dlp-policies-for-power-bi-overview.md)|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png) |![Image of "Available" button.](../media/yes.png)|
+|[Data Loss Prevention policies](/fabric/governance/data-loss-prevention-overview)|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png) |![Image of "Available" button.](../media/yes.png)|
 |[Data Protection (MIP labels)](./service-security-sensitivity-label-overview.md)|![Image of "Available" button.](../media/yes.png)|![Image of "Available" button.](../media/yes.png) |![Image of "Available" button.](../media/yes.png)|
 |[Dataflows - Direct Query](../transform-model/dataflows/dataflows-configure-consume.md) | ![Image of "Available" button.](../media/yes.png) |![Image of "Available" button.](../media/yes.png)|Not planned |
 |[Dataflows - SQL Compute engine optimization](../transform-model/dataflows/dataflows-premium-features.md) | ![Image of "Available" button.](../media/yes.png) |![Image of "Available" button.](../media/yes.png)|Not planned |