#PRINCIPAL DATA FEED INSTACAL REGISTRATION#
#PRINCIPAL DATA FEED INSTACAL CODE#
#PRINCIPAL DATA FEED INSTACAL LICENSE#

Learn more about SAP Principal Propagation from this SAP community post and this video series.Ĭontinue to choose at which level the authentication settings should be applied by Power Query on Excel. For more information about the configuration, see this Microsoft tutorial. Supply the Azure AD account that is mapped to the named SAP user on the SAP Gateway using SAP Principal Propagation. Switch the login method to Organizational account and click Sign in. Below example shows the integration experience with Excel Desktop. Retrieve the Base URL and insert in your target application. Finally add it to Azure API Management using the official OData import guide. Discover or activate it using SAP transaction /IWFND/MAINT_SERVICE. Below example uses the SAP Gateway demo service GWSAMPLE_BASIC. Add a new OData source to the Excel sheet via the Data ribbon (Get Data -> From Other Sources -> From OData Feed). With the given configuration, the built-in authentication mechanism of Power Query becomes available to the exposed OData APIs. SAP OData authentication via Power Query on Excel Desktop Regarding securing SAP APIs with Azure, see this article. See below a snippet from the mentioned policy: įor more information about secure SAP access from the Internet and SAP perimeter network design, see this guide. In addition to the support of the Organizational Account login flow, the policy supports OData URL response rewriting because the target server replies with original URLs. Find the used client ID for Power Query here. See below a snippet from that policy highlighting the authentication mechanism. Use this Azure API Management policy for your target OData API to support Power Query's authentication flow. Azure API Management policy design for Power Query If custom domain for Azure API Management isn't an option for you, you need to use a custom Power Query Connector instead.

#PRINCIPAL DATA FEED INSTACAL REGISTRATION#

The respective Azure AD application registration for the Azure API Management tenant would look like below. To prove domain name ownership and grant access to the certificate, add those DNS records to your Azure App Service Domain as below: For more information, see the custom domain documentation. For more domain certificate options, see the Azure API Management documentation.Ĭomplete the setup of your custom domain as per the domain requirements. See below the screenshot of an example configuration in API Management using a custom domain called with a managed certificate and Azure App Service Domain. Azure API Management custom domain configuration For more information, see SAP's OData configuration.

#PRINCIPAL DATA FEED INSTACAL CODE#

Discover and activate available services via SAP transaction code /IWFND/MAINT_SERVICE. SAP Gateway needs to be configured to expose the desired target OData services. Configure a custom domain for Azure API Management to meet the requirement. Power Query requires matching API service URL and Azure AD application ID URL. On-premises installations require a hybrid deployment to apply the approach as is using the Azure API Management self-hosted Gateway. Internal refers to instances that are fully restricted to a private virtual network whereas external retains public access to Azure API Management.

Network access solutions such as VPN aren't in scope for apps like Excel for the web.Īzure API Management reflects local and web-based environment needs with different deployment modes that can be applied to Azure landscapes ( internal The client execution environment needs to be considered for the network path between the client application and the target SAP workload. Setup considerationsĮnd users have a choice between local desktop or web-based clients (for instance Excel or Power BI). Address on-premises landscapes with the Azure API Management self-hosted Gateway.įor more information on which Microsoft products support Power Query in general, see the Power Query documentation. 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. SAP Analytics Cloud, add-in for Microsoft OfficeĪccess SAP Data Warehouse Cloud with Microsoft ExcelĬustom Excel Macros to interact with SAP back endsĮxport from SAP List Viewer (ALV) to Microsoft Excel SAP Analysis for Microsoft Office Excel and PowerPoint

Integrations between SAP products and the Microsoft 365 portfolio range from custom codes, and partner add-ons to fully customized Office products. Overview of Microsoft products with SAP integration

#PRINCIPAL DATA FEED INSTACAL LICENSE#

For any SAP license related questions please contact your SAP representative. Note: SAP Principal Propagation ensures user-mapping to the licensed named SAP user.

Principal data feed instacal