From bf8e75ae8d36f111d5501f7a6278dac206f0c9e2 Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Thu, 22 Aug 2024 11:26:20 +0300 Subject: [PATCH 1/9] Note for ADFS configuration --- powerbi-docs/report-server/mobile-oauth-ssrs.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index 58114bf344..183a8c2207 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -71,6 +71,9 @@ For more information, see [Modify a Reporting Services Configuration File](/sql/ You need to configure ADFS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). +> [!IMPORTANT] +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Service 2019 or later, or use Microsoft Entra application proxy. + ### Create an application group Within the AD FS Management screen, you want to create an application group for Reporting Services that includes information for the Power BI Mobile apps. From 6c5ff0df1c8fb103eb771108eb3914a27b84c087 Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Thu, 22 Aug 2024 11:33:15 +0300 Subject: [PATCH 2/9] Updated text --- .../report-server/connect-adfs-wap-report-server.md | 9 ++++++--- powerbi-docs/report-server/mobile-oauth-ssrs.md | 2 +- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/powerbi-docs/report-server/connect-adfs-wap-report-server.md b/powerbi-docs/report-server/connect-adfs-wap-report-server.md index 87880f88cc..97d43cccef 100644 --- a/powerbi-docs/report-server/connect-adfs-wap-report-server.md +++ b/powerbi-docs/report-server/connect-adfs-wap-report-server.md @@ -56,11 +56,14 @@ To enable a report server to use Kerberos authentication, you need to configure For more information, see [Modify a Reporting Services Configuration File](/sql/reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config) and [Configure Windows Authentication on a Report Server](/sql/reporting-services/security/configure-windows-authentication-on-the-report-server). -## 2. Configure Active Directory Federation Services (AD FS) +## 2. Configure Active Directory Federation Services (ADFS) -You need to configure AD FS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). +You need to configure ADFS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). -On the AD FS server, using AD FS Management App, complete these steps. +> [!IMPORTANT] +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. + +On the ADFS server, using ADFS Management App, complete these steps. 1. Right-click **Relying Party Trusts** > **Add Relying Party Trust**. diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index 183a8c2207..e41228156c 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -72,7 +72,7 @@ For more information, see [Modify a Reporting Services Configuration File](/sql/ You need to configure ADFS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). > [!IMPORTANT] -> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Service 2019 or later, or use Microsoft Entra application proxy. +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. ### Create an application group From 246fe59bc5f1507cca612305dbf5d6ce5de73f01 Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Mon, 26 Aug 2024 01:00:16 +0300 Subject: [PATCH 3/9] Text changes --- .../report-server/connect-adfs-wap-report-server.md | 8 ++++++-- powerbi-docs/report-server/mobile-oauth-ssrs.md | 12 ++++++++---- 2 files changed, 14 insertions(+), 6 deletions(-) diff --git a/powerbi-docs/report-server/connect-adfs-wap-report-server.md b/powerbi-docs/report-server/connect-adfs-wap-report-server.md index 97d43cccef..d59bb685ff 100644 --- a/powerbi-docs/report-server/connect-adfs-wap-report-server.md +++ b/powerbi-docs/report-server/connect-adfs-wap-report-server.md @@ -7,13 +7,17 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-report-server ms.topic: how-to -ms.date: 12/05/2023 +ms.date: 08/26/2024 --- # Use Web Application Proxy and Active Directory Federated Services - Power BI Report Server This article discusses how to use Web Application Proxy (WAP) and Active Directory Federated Services (AD FS) to connect to Power BI Report Server, and SQL Server Reporting Services (SSRS) 2016 and later. Through this integration, users who are away from the corporate network can access their Power BI Report Server and Reporting Services reports from their client browsers and be protected by AD FS preauthentication. For the Power BI mobile apps, see also [Connect to Report Server and SSRS from Power BI mobile applications](./mobile-oauth-ssrs.md). + +> [!NOTE] +> As of March 1st, 2025, due to a change in the authentication library it uses, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, users may have to re-sign in to Report Server. + > [!NOTE] > The configuration described in this article is no longer the preferred method of connecting to Power BI Report Server and SQL Server Reporting Services (SSRS) 2016 and later. Configure the connection using using Microsoft Entra application proxy instead, as described in [Configure Power BI Report Server with Microsoft Entra application proxy](./microsoft-entra-application-proxy.md) @@ -61,7 +65,7 @@ For more information, see [Modify a Reporting Services Configuration File](/sql/ You need to configure ADFS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). > [!IMPORTANT] -> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. See the [note](#windows-server-upgrade-note) at the beginning of this article.. On the ADFS server, using ADFS Management App, complete these steps. diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index e41228156c..3355ecfd0d 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-mobile ms.topic: how-to -ms.date: 07/18/2024 +ms.date: 08/26/2024 --- # Connect to Power BI Report Server and SSRS from Power BI mobile applications @@ -16,10 +16,14 @@ This article discusses how to configure your environment to support OAuth authen ## Requirements -Windows Server 2016 is required for the Web Application Proxy (WAP) and Active Directory Federation Services (ADFS) servers. You don't need to have a Windows 2016 functional level domain. +Windows Server is required for the Web Application Proxy (WAP) and Active Directory Federation Services (ADFS) servers. You don't need to have a Windows 2016 functional level domain. In order for users to be able to add a report server connection to their Power BI mobile app, you must grant them access to the report server's home folder. + +> [!NOTE] +> As of March 1st, 2025, due to a change in the authentication library it uses, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, users may have to re-sign in to Report Server. + ## Domain Name Services (DNS) configuration The public URL is the URL that the Power BI mobile app will connect to. For example, it might look similar to the following. @@ -69,10 +73,10 @@ For more information, see [Modify a Reporting Services Configuration File](/sql/ ## Active Directory Federation Services (ADFS) Configuration -You need to configure ADFS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). +You need to configure ADFS on a Windows server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). > [!IMPORTANT] -> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. See the [note](#windows-server-upgrade-note) at the beginning of this article. ### Create an application group From 2ea1ec8663f4b1303e026c0b20201ee0556aa31b Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Mon, 26 Aug 2024 15:05:59 +0300 Subject: [PATCH 4/9] Misc changes --- .../connect-adfs-wap-report-server.md | 14 +++--- .../report-server/mobile-oauth-ssrs.md | 44 ++++++++++--------- 2 files changed, 31 insertions(+), 27 deletions(-) diff --git a/powerbi-docs/report-server/connect-adfs-wap-report-server.md b/powerbi-docs/report-server/connect-adfs-wap-report-server.md index d59bb685ff..a02c74587f 100644 --- a/powerbi-docs/report-server/connect-adfs-wap-report-server.md +++ b/powerbi-docs/report-server/connect-adfs-wap-report-server.md @@ -16,7 +16,9 @@ This article discusses how to use Web Application Proxy (WAP) and Active Directo > [!NOTE] -> As of March 1st, 2025, due to a change in the authentication library it uses, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, users may have to re-sign in to Report Server. +> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers will have to upgrade their AD FS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. +> +> This upgrade is necessitated by a change in the authentication library used by the mobile app. The change in no way affects Microsoft support for AD FS on Windows Server 2016, but rather only the ability of the Power BI Mobile app to connect to it. > [!NOTE] > The configuration described in this article is no longer the preferred method of connecting to Power BI Report Server and SQL Server Reporting Services (SSRS) 2016 and later. Configure the connection using using Microsoft Entra application proxy instead, as described in [Configure Power BI Report Server with Microsoft Entra application proxy](./microsoft-entra-application-proxy.md) @@ -60,14 +62,14 @@ To enable a report server to use Kerberos authentication, you need to configure For more information, see [Modify a Reporting Services Configuration File](/sql/reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config) and [Configure Windows Authentication on a Report Server](/sql/reporting-services/security/configure-windows-authentication-on-the-report-server). -## 2. Configure Active Directory Federation Services (ADFS) +## 2. Configure Active Directory Federation Services (AD FS) -You need to configure ADFS on a Windows 2016 server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). +You need to configure AD FS on a Windows server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). > [!IMPORTANT] -> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. See the [note](#windows-server-upgrade-note) at the beginning of this article.. +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. See the [note](#windows-server-upgrade-note) at the beginning of this article. -On the ADFS server, using ADFS Management App, complete these steps. +On the AD FS server, using AD FS Management App, complete these steps. 1. Right-click **Relying Party Trusts** > **Add Relying Party Trust**. @@ -98,7 +100,7 @@ On the ADFS server, using ADFS Management App, complete these steps. ## 3. Configure Web Application Proxy (WAP) -You want to enable the Web Application Proxy (Role) Windows role on a server in your environment. It must be on a Windows 2016 server. For more information, see [Web Application Proxy in Windows Server 2016](/windows-server/remote/remote-access/web-application-proxy/web-application-proxy-windows-server) and [Publishing Applications using AD FS Preauthentication](/windows-server/remote/remote-access/web-application-proxy/Publishing-Applications-using-AD-FS-Preauthentication#BKMK_1.2). +You want to enable the Web Application Proxy (Role) Windows role on a server in your environment. It must be a Windows server. For more information, see [Web Application Proxy in Windows Server](/windows-server/remote/remote-access/web-application-proxy/web-application-proxy-windows-server) and [Publishing Applications using AD FS Preauthentication](/windows-server/remote/remote-access/web-application-proxy/Publishing-Applications-using-AD-FS-Preauthentication#BKMK_1.2). ### Configure constrained delegation diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index 3355ecfd0d..deb45c6c2e 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -16,13 +16,15 @@ This article discusses how to configure your environment to support OAuth authen ## Requirements -Windows Server is required for the Web Application Proxy (WAP) and Active Directory Federation Services (ADFS) servers. You don't need to have a Windows 2016 functional level domain. +Windows Server is required for the Web Application Proxy (WAP) and Active Directory Federation Services (AD FS) servers. You don't need to have a Windows functional level domain. In order for users to be able to add a report server connection to their Power BI mobile app, you must grant them access to the report server's home folder. > [!NOTE] -> As of March 1st, 2025, due to a change in the authentication library it uses, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. Customers will have to upgrade their ADFS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, users may have to re-sign in to Report Server. +> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers will have to upgrade their AD FS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. +> +> This upgrade is necessitated by a change in the authentication library used by the mobile app. The change in no way affects Microsoft support for AD FS on Windows Server 2016, but rather only the ability of the Power BI Mobile app to connect to it. ## Domain Name Services (DNS) configuration @@ -32,7 +34,7 @@ The public URL is the URL that the Power BI mobile app will connect to. For exam https://reports.contoso.com ``` -Your DNS record for **reports** to the public IP address of the Web Application Proxy (WAP) server. You also need to configure a public DNS record for your ADFS server. For example, you might have configured the ADFS server with the following URL. +Your DNS record for **reports** to the public IP address of the Web Application Proxy (WAP) server. You also need to configure a public DNS record for your AD FS server. For example, you might have configured the AD FS server with the following URL. ```https https://fs.contoso.com @@ -42,7 +44,7 @@ Your DNS record for **fs** to the public IP address of the Web Application Proxy ## Certificates -You need to configure certificates for both the WAP application and the ADFS server. Both of these certificates must be part of a valid certificate authority that your mobile devices recognize. +You need to configure certificates for both the WAP application and the AD FS server. Both of these certificates must be part of a valid certificate authority that your mobile devices recognize. ## Reporting Services configuration @@ -71,12 +73,12 @@ To enable a report server to use Kerberos authentication, you need to configure For more information, see [Modify a Reporting Services Configuration File](/sql/reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config) and [Configure Windows Authentication on a Report Server](/sql/reporting-services/security/configure-windows-authentication-on-the-report-server). -## Active Directory Federation Services (ADFS) Configuration +## Active Directory Federation Services (AD FS) Configuration -You need to configure ADFS on a Windows server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). +You need to configure AD FS on a Windows server within your environment. The configuration can be done through the Server Manager and selecting Add Roles and Features under Manage. For more information, see [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services). > [!IMPORTANT] -> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through ADFS configured on Windows Server 2016. See the [note](#windows-server-upgrade-note) at the beginning of this article. +> As of March 1st, 2025, the Power BI Mobile apps will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. See the [note](#windows-server-upgrade-note) at the beginning of this article. ### Create an application group @@ -86,11 +88,11 @@ You can create the application group with the following steps. 1. Within the AD FS Management app, right-click **Application Groups** and select **Add Application Group…** - ![ADFS Add Application](media/mobile-oauth-ssrs/adfs-add-application-group.png) + ![AD FS Add Application](media/mobile-oauth-ssrs/adfs-add-application-group.png) 2. Within the Add Application Group Wizard, provide a **name** for the application group and select **Native application accessing a web API**. - ![ADFS Application Group Wizard 01](media/mobile-oauth-ssrs/adfs-application-group-wizard1.png) + ![AD FS Application Group Wizard 01](media/mobile-oauth-ssrs/adfs-application-group-wizard1.png) 3. Select **Next**. @@ -109,7 +111,7 @@ You can create the application group with the following steps. **Android Apps only need the following steps:** urn:ietf:wg:oauth:2.0:oob - ![ADFS Application Group Wizard 02](media/mobile-oauth-ssrs/adfs-application-group-wizard2.png) + ![AD FS Application Group Wizard 02](media/mobile-oauth-ssrs/adfs-application-group-wizard2.png) 7. Select **Next**. 8. Supply the URL for your Report Server. The URL is the external URL that will hit your Web Application Proxy. It should be in the following format. @@ -119,12 +121,12 @@ You can create the application group with the following steps. `https:///reports` - ![ADFS Application Group Wizard 03](media/mobile-oauth-ssrs/adfs-application-group-wizard3.png) + ![AD FS Application Group Wizard 03](media/mobile-oauth-ssrs/adfs-application-group-wizard3.png) 9. Select **Next**. 10. Choose the **Access Control Policy** that fits your organization's needs. - ![ADFS Application Group Wizard 04](media/mobile-oauth-ssrs/adfs-application-group-wizard4.png) + ![AD FS Application Group Wizard 04](media/mobile-oauth-ssrs/adfs-application-group-wizard4.png) 11. Select **Next**. @@ -136,9 +138,9 @@ You can create the application group with the following steps. When completed, you should see the properties of your application group look similar to the following. -![ADFS Application Group Wizard](media/mobile-oauth-ssrs/adfs-application-group.png) +![AD FS Application Group Wizard](media/mobile-oauth-ssrs/adfs-application-group.png) -Now run the following PowerShell command on the ADFS server to ensure that token refresh is supported. +Now run the following PowerShell command on the AD FS server to ensure that token refresh is supported. ```powershell Set-AdfsApplicationPermission -TargetClientRoleIdentifier '484d54fc-b481-4eee-9505-0258a1913020' -AddScope 'openid' @@ -146,7 +148,7 @@ Set-AdfsApplicationPermission -TargetClientRoleIdentifier '484d54fc-b481-4eee-95 ## Web Application Proxy (WAP) Configuration -You want to enable the Web Application Proxy (Role) Windows role on a server in your environment. It must be on a Windows 2016 server. For more information, see [Web Application Proxy in Windows Server 2016](/windows-server/remote/remote-access/web-application-proxy/web-application-proxy-windows-server) and [Publishing Applications using AD FS Preauthentication](/windows-server/remote/remote-access/web-application-proxy/Publishing-Applications-using-AD-FS-Preauthentication#a-namebkmk14apublish-an-application-that-uses-oauth2-such-as-a-windows-store-app). +You want to enable the Web Application Proxy (Role) Windows role on a server in your environment. It must be on a Windows server. For more information, see [Web Application Proxy in Windows Server](/windows-server/remote/remote-access/web-application-proxy/web-application-proxy-windows-server) and [Publishing Applications using AD FS Preauthentication](/windows-server/remote/remote-access/web-application-proxy/Publishing-Applications-using-AD-FS-Preauthentication#a-namebkmk14apublish-an-application-that-uses-oauth2-such-as-a-windows-store-app). ### Constrained delegation configuration @@ -201,7 +203,7 @@ Add-WebApplicationProxyApplication -Name "Contoso Reports" -ExternalPreauthentic | Parameter | Comments | | --- | --- | -| **ADFSRelyingPartyName** |The Web API name that you created as part of the Application Group within ADFS. | +| **ADFSRelyingPartyName** |The Web API name that you created as part of the Application Group within AD FS. | | **ExternalCertificateThumbprint** |The certificate to use for the external users. It's important that the certificate is valid on mobile devices and come from a trusted certificate authority. | | **BackendServerUrl** |The URL to the Report Server from the WAP server. If the WAP server is in a DMZ, you might need to use a fully qualified domain name. Make sure you can hit this URL from the web browser on the WAP server. | | **BackendServerAuthenticationSPN** |The SPN you created as part of the Reporting Services configuration. | @@ -230,9 +232,9 @@ Within the Power BI mobile app, you want to connect to your Reporting Services i ![Type the server address](media/mobile-oauth-ssrs/powerbi-mobile-app1.png) -When you select **Connect**, you'll be directed to your ADFS sign-in page. Enter valid credentials for your domain. +When you select **Connect**, you'll be directed to your AD FS sign-in page. Enter valid credentials for your domain. -![Sign-in to ADFS](media/mobile-oauth-ssrs/powerbi-mobile-app2.png) +![Sign-in to AD FS](media/mobile-oauth-ssrs/powerbi-mobile-app2.png) After you select **Sign in**, you see the elements from your Reporting Services server. @@ -248,7 +250,7 @@ You can enable multifactor authentication to enable additional security for your You can set up [Fiddler](https://www.telerik.com/fiddler) to act as a proxy for your mobile devices to see how far the request made it. To enable a Fiddler proxy for your phone device, you need to set up the [CertMaker for iOS and Android](https://www.telerik.com/fiddler/add-ons) on the machine running Fiddler. The add-on is from Telerik for Fiddler. -If the sign-in works successfully when using Fiddler, you might have a certificate issue with either the WAP application or the ADFS server. +If the sign-in works successfully when using Fiddler, you might have a certificate issue with either the WAP application or the AD FS server. ## Related content @@ -256,7 +258,7 @@ If the sign-in works successfully when using Fiddler, you might have a certifica * [Modify a Reporting Services Configuration File](/sql/reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config) * [Configure Windows Authentication on a Report Server](/sql/reporting-services/security/configure-windows-authentication-on-the-report-server) * [Active Directory Federation Services](/windows-server/identity/active-directory-federation-services) -* [Web Application Proxy in Windows Server 2016](/windows-server/remote/remote-access/web-application-proxy/web-application-proxy-windows-server) +* [Web Application Proxy in Windows Server](/windows-server/remote/remote-access/web-application-proxy/web-application-proxy-windows-server) * [Publishing Applications using AD FS Preauthentication](/windows-server/remote/remote-access/web-application-proxy/Publishing-Applications-using-AD-FS-Preauthentication#a-namebkmk14apublish-an-application-that-uses-oauth2-such-as-a-windows-store-app) -* [Configure AD FS 2016 and Microsoft Entra multifactor authentication](/windows-server/identity/ad-fs/operations/configure-ad-fs-and-azure-mfa) +* [Configure Microsoft Entra multifactor authentication as authentication provider using AD FS](/windows-server/identity/ad-fs/operations/configure-ad-fs-and-azure-mfa) More questions? [Try the Power BI Community](https://community.powerbi.com/) From 1d9372f30a23bfd346af26354c01a761e2cc3f3b Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Tue, 27 Aug 2024 18:56:55 +0300 Subject: [PATCH 5/9] Changes as per PM review --- powerbi-docs/report-server/connect-adfs-wap-report-server.md | 4 ++-- powerbi-docs/report-server/mobile-oauth-ssrs.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/powerbi-docs/report-server/connect-adfs-wap-report-server.md b/powerbi-docs/report-server/connect-adfs-wap-report-server.md index a02c74587f..2cc1615cda 100644 --- a/powerbi-docs/report-server/connect-adfs-wap-report-server.md +++ b/powerbi-docs/report-server/connect-adfs-wap-report-server.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-report-server ms.topic: how-to -ms.date: 08/26/2024 +ms.date: 08/27/2024 --- # Use Web Application Proxy and Active Directory Federated Services - Power BI Report Server @@ -16,7 +16,7 @@ This article discusses how to use Web Application Proxy (WAP) and Active Directo > [!NOTE] -> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers will have to upgrade their AD FS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. +> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers who use OAuth with AD FS configured on Windows Server 2016 and Web Application Proxy (WAP) will have to upgrade their AD FS server to Windows Server 2019 or later, or use [Microsoft Entra application proxy](./microsoft-entra-application-proxy.md). After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. > > This upgrade is necessitated by a change in the authentication library used by the mobile app. The change in no way affects Microsoft support for AD FS on Windows Server 2016, but rather only the ability of the Power BI Mobile app to connect to it. diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index deb45c6c2e..79134fb0fa 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-mobile ms.topic: how-to -ms.date: 08/26/2024 +ms.date: 08/27/2024 --- # Connect to Power BI Report Server and SSRS from Power BI mobile applications @@ -22,7 +22,7 @@ In order for users to be able to add a report server connection to their Power B > [!NOTE] -> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers will have to upgrade their AD FS server to Windows Server 2019 or later, or use Microsoft Entra application proxy. After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. +> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers who use OAuth with AD FS configured on Windows Server 2016 and Web Application Proxy (WAP) will have to upgrade their AD FS server to Windows Server 2019 or later, or use [Microsoft Entra application proxy](./microsoft-entra-application-proxy.md). After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. > > This upgrade is necessitated by a change in the authentication library used by the mobile app. The change in no way affects Microsoft support for AD FS on Windows Server 2016, but rather only the ability of the Power BI Mobile app to connect to it. From e957b1ee96aeb8bcbb4035685a1fb2333120116f Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Wed, 28 Aug 2024 16:40:11 +0300 Subject: [PATCH 6/9] Addition as per PM feedback --- powerbi-docs/report-server/connect-adfs-wap-report-server.md | 4 ++-- powerbi-docs/report-server/mobile-oauth-ssrs.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/powerbi-docs/report-server/connect-adfs-wap-report-server.md b/powerbi-docs/report-server/connect-adfs-wap-report-server.md index 2cc1615cda..696b80c18a 100644 --- a/powerbi-docs/report-server/connect-adfs-wap-report-server.md +++ b/powerbi-docs/report-server/connect-adfs-wap-report-server.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-report-server ms.topic: how-to -ms.date: 08/27/2024 +ms.date: 08/28/2024 --- # Use Web Application Proxy and Active Directory Federated Services - Power BI Report Server @@ -16,7 +16,7 @@ This article discusses how to use Web Application Proxy (WAP) and Active Directo > [!NOTE] -> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers who use OAuth with AD FS configured on Windows Server 2016 and Web Application Proxy (WAP) will have to upgrade their AD FS server to Windows Server 2019 or later, or use [Microsoft Entra application proxy](./microsoft-entra-application-proxy.md). After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. +> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server using the OAuth protocol through AD FS configured on Windows Server 2016. Customers who use OAuth with AD FS configured on Windows Server 2016 and Web Application Proxy (WAP) will have to upgrade their AD FS server to Windows Server 2019 or later, or use [Microsoft Entra application proxy](./microsoft-entra-application-proxy.md). After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. > > This upgrade is necessitated by a change in the authentication library used by the mobile app. The change in no way affects Microsoft support for AD FS on Windows Server 2016, but rather only the ability of the Power BI Mobile app to connect to it. diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index 79134fb0fa..1bf0112a5b 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-mobile ms.topic: how-to -ms.date: 08/27/2024 +ms.date: 08/28/2024 --- # Connect to Power BI Report Server and SSRS from Power BI mobile applications @@ -22,7 +22,7 @@ In order for users to be able to add a report server connection to their Power B > [!NOTE] -> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server through AD FS configured on Windows Server 2016. Customers who use OAuth with AD FS configured on Windows Server 2016 and Web Application Proxy (WAP) will have to upgrade their AD FS server to Windows Server 2019 or later, or use [Microsoft Entra application proxy](./microsoft-entra-application-proxy.md). After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. +> As of March 1st, 2025, the Power BI Mobile app will no longer be able to connect to Report Server using the OAuth protocol through AD FS configured on Windows Server 2016. Customers who use OAuth with AD FS configured on Windows Server 2016 and Web Application Proxy (WAP) will have to upgrade their AD FS server to Windows Server 2019 or later, or use [Microsoft Entra application proxy](./microsoft-entra-application-proxy.md). After the Windows Server upgrade, Power BI Mobile app users may have to re-sign in to Report Server. > > This upgrade is necessitated by a change in the authentication library used by the mobile app. The change in no way affects Microsoft support for AD FS on Windows Server 2016, but rather only the ability of the Power BI Mobile app to connect to it. From ff86128c61df01d3176a40813f47b3d7bbd6b74e Mon Sep 17 00:00:00 2001 From: Alma Jenks Date: Wed, 28 Aug 2024 16:21:45 -0700 Subject: [PATCH 7/9] Update .acrolinx-config.edn March 2023 Updated Guidelines - MS is deprecated. Switching to Microsoft Standard. --- .acrolinx-config.edn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.acrolinx-config.edn b/.acrolinx-config.edn index 88b4dc3a61..60ccec390b 100644 --- a/.acrolinx-config.edn +++ b/.acrolinx-config.edn @@ -1,7 +1,7 @@ {:allowed-branchname-matches ["main" "release-.*"] :allowed-filename-matches ["powerbi-docs/"] - :guidance-profile "1889ea46-76de-460c-a27c-6667b60e201e" ;; testing March 2023 updated guidelines - Microsoft standard. + :guidance-profile "ddd70715-fa0d-3b81-98b1-11d94b0e731a" ;; Microsoft standard. :template-header ;; This displays in the pull request results pane. " From 03857a766550dc3c9a9d6ebb186b957c791bd8fa Mon Sep 17 00:00:00 2001 From: Paul Inbar <54644589+paulinbar@users.noreply.github.com> Date: Thu, 29 Aug 2024 14:17:41 +0300 Subject: [PATCH 8/9] Updated date before publishing --- powerbi-docs/report-server/connect-adfs-wap-report-server.md | 2 +- powerbi-docs/report-server/mobile-oauth-ssrs.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/powerbi-docs/report-server/connect-adfs-wap-report-server.md b/powerbi-docs/report-server/connect-adfs-wap-report-server.md index 696b80c18a..bcd4083d5c 100644 --- a/powerbi-docs/report-server/connect-adfs-wap-report-server.md +++ b/powerbi-docs/report-server/connect-adfs-wap-report-server.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-report-server ms.topic: how-to -ms.date: 08/28/2024 +ms.date: 08/29/2024 --- # Use Web Application Proxy and Active Directory Federated Services - Power BI Report Server diff --git a/powerbi-docs/report-server/mobile-oauth-ssrs.md b/powerbi-docs/report-server/mobile-oauth-ssrs.md index 1bf0112a5b..49718bad4d 100644 --- a/powerbi-docs/report-server/mobile-oauth-ssrs.md +++ b/powerbi-docs/report-server/mobile-oauth-ssrs.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-mobile ms.topic: how-to -ms.date: 08/28/2024 +ms.date: 08/29/2024 --- # Connect to Power BI Report Server and SSRS from Power BI mobile applications From 4c0deea2b84b262aafdf6277416e3178ac5db158 Mon Sep 17 00:00:00 2001 From: Maggie Sparkman <12401230+maggiesMSFT@users.noreply.github.com> Date: Thu, 29 Aug 2024 13:09:36 -0700 Subject: [PATCH 9/9] Update service-modern-usage-metrics.md delete Postman --- .../collaborate-share/service-modern-usage-metrics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/powerbi-docs/collaborate-share/service-modern-usage-metrics.md b/powerbi-docs/collaborate-share/service-modern-usage-metrics.md index 1cc1f20ec9..a158e235d4 100644 --- a/powerbi-docs/collaborate-share/service-modern-usage-metrics.md +++ b/powerbi-docs/collaborate-share/service-modern-usage-metrics.md @@ -8,7 +8,7 @@ featuredvideoid: '' ms.service: powerbi ms.subservice: pbi-collaborate-share ms.topic: conceptual -ms.date: 02/15/2024 +ms.date: 08/29/2024 LocalizationGroup: Dashboards --- @@ -430,7 +430,7 @@ Follow these steps to delete the semantic model and then create a fresh data ref > [!NOTE] > This **Try it** button does not apply to GCC customers since their API endpoint is different. - You can use this API to delete the semantic model. You can use Postman or other API tools to make an API call on this endpoint to delete the semantic model. + You can use this API to delete the semantic model. You can use API tools to make an API call on this endpoint to delete the semantic model. 1. If you don't see a **Try it** button, use the trigger **Scheduled cloud flow**. Select a starting time and run it every hour. Then refresh the semantic model. Let the flow run once, then switch off the flow. Read more about [cloud flows in Power Automate](/power-automate/run-scheduled-tasks).