Skip to content

Commit 1013f1e

Browse files
authored
Broken link fixed
1 parent bb4feb6 commit 1013f1e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/workloads/sap/expose-sap-odata-to-power-query.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Integrations between SAP products and the Microsoft 365 portfolio range from cus
4040

4141
The mechanism described in this article uses the standard built-in OData capabilities of Power Query and puts emphasis for SAP landscapes deployed on Azure. Address on-premises landscapes with the Azure API Management [self-hosted Gateway](../../../api-management/self-hosted-gateway-overview.md).
4242

43-
For more information on which Microsoft products support Power Query, see [the Power Query documentation](/power-query-what-is-power-query#where-can-you-use-power-query).
43+
For more information on which Microsoft products support Power Query, see [the Power Query documentation](/power-query/power-query-what-is-power-query#where-can-you-use-power-query).
4444

4545
## Setup considerations
4646

@@ -185,4 +185,4 @@ The highlighted button triggers a flow that forwards the OData PATCH request to
185185

186186
[Understand Azure Application Gateway and Web Application Firewall for SAP](https://blogs.sap.com/2020/12/03/sap-on-azure-application-gateway-web-application-firewall-waf-v2-setup-for-internet-facing-sap-fiori-apps/)
187187

188-
[Automate API deployments with APIOps](/azure/architecture/example-scenario/devops/automated-api-deployments-apiops)
188+
[Automate API deployments with APIOps](/azure/architecture/example-scenario/devops/automated-api-deployments-apiops)

0 commit comments

Comments
 (0)