Placeholder image

Updates to the SAP Landing Zone Accelerator

| Pankaj Meshram |



Episode #217

Introduction

In episode 217 of our SAP on Azure video podcast we talk about the SAP on Azure Landing Zone Accelerator.

Over two years ago we had already talked about the SAP Landing Zone Accelerator. The idea is to help customers get started with their SAP systems on Azure. In the meantime a lot of things have happened. The documentation is constantly evolving and a lot of new things have been added. We not only cover pure infrastrucutre, but also SAP and Data or SAP and Power Platform. In order to give us an update on what’s new, I am happy to have Pankaj Meshram again with us to talk about the SAP on Azure landing zone accelerator.

Find all the links mentioned here: https://www.saponazurepodcast.de/episode217

Reach out to us for any feedback / questions:

#Microsoft #SAP #Azure #SAPonAzure #PowerPlatform #PowerSAP

Summary created by AI

  • Introduction and Overview:
  • Holger introduced the podcast episode and welcomed Pankaj to discuss the SAP on Azure Landing Zone accelerator, highlighting its evolution and the addition of new content.
    • Podcast Introduction: Holger introduced episode 217 of the SAP on Azure Video podcast, mentioning the date (November 13th) and the co-hosts, Robert and Goran. He welcomed Pankaj to discuss the SAP on Azure Landing Zone accelerator.
    • Landing Zone Evolution: Holger highlighted that the SAP Landing Zone accelerator was discussed over two years ago and has since evolved significantly, with continuous updates and new content additions.
  • Pankaj’s Role and Contributions:
  • Pankaj explained their role in the global customer success unit, focusing on the technical strategy of SAP on Azure workloads, and acknowledged the contributions from various parts of Microsoft.
    • Pankaj’s Role: Pankaj Meshram introduced himself as part of the global customer success unit, responsible for the technical strategy of SAP on Azure workloads from the CSU side.
    • Microsoft Contributions: Pankaj acknowledged the contributions from various parts of Microsoft, emphasizing the collaborative “one Microsoft” approach in developing the SAP on Azure Landing Zone accelerator.
  • Purpose of the SAP on Azure Landing Zone Accelerator:
  • Pankaj described the SAP on Azure Landing Zone accelerator as a collection of best practices for architecting SAP solutions on Azure, covering various design areas like networking, identity, security, and governance.
    • Best Practices Collection: Pankaj described the SAP on Azure Landing Zone accelerator as a collection of best practices for architecting SAP solutions on Azure, covering areas such as networking, identity, security, and governance.
    • Design Guidelines: Pankaj explained that the accelerator includes detailed design guidelines for various areas, ensuring customers leverage best practices when architecting their SAP solutions on Azure.
  • Evolution and Updates:
  • Pankaj discussed the continuous updates and evolution of the landing zone accelerator, incorporating new capabilities and offerings based on customer feedback and market conditions.
    • Continuous Updates: Pankaj highlighted that the SAP on Azure Landing Zone accelerator is continuously updated to incorporate new capabilities and offerings, reflecting changes in products, services, and market conditions.
    • Customer Feedback: Pankaj emphasized the role of customer feedback in driving updates and improvements to the landing zone accelerator, ensuring it meets evolving customer needs.
  • Innovating with SAP on Azure:
  • Pankaj highlighted the focus on innovation with SAP on Azure, including integration with data, power platform, and AI copilot, driven by customer feedback and engineering product groups.
    • Innovation Focus: Pankaj discussed the focus on innovation with SAP on Azure, including integrating SAP with data, the power platform, and AI copilot, driven by customer feedback and engineering product groups.
    • Integration Areas: Pankaj mentioned specific areas of innovation, such as SAP with data, SAP with the power platform, and SAP with AI copilot, highlighting the importance of these integrations for customers.
  • SAP and Power Platform Integration:
  • Pankaj introduced new articles on integrating SAP with Microsoft Power Platform, providing fundamental information about extending SAP applications using power platform components like Power Apps, Power Automate, and Power BI.
    • New Articles: Pankaj introduced new articles on integrating SAP with Microsoft Power Platform, providing fundamental information about extending SAP applications using components like Power Apps, Power Automate, and Power BI.
    • Power Platform Components: Pankaj explained the various components of the Power Platform, including Power Apps, Power Automate, Power BI, and AI Builder, and their relevance to extending SAP applications.
  • Detailed Design Guidelines:
  • Pankaj showcased detailed design guidelines for integrating SAP with Power Platform, including connectivity options, security mechanisms, and architecture examples.
    • Connectivity Options: Pankaj detailed the connectivity options for integrating SAP with Power Platform, including the use of SAP connectors, API gateways, and on-premise data gateways.
    • Security Mechanisms: Pankaj discussed the security mechanisms involved in the integration, such as using Azure API management and ensuring compliance with security standards.
    • Architecture Examples: Pankaj provided examples of architecture designs for integrating SAP with Power Platform, illustrating how different components and connectors fit into the overall landscape.
  • Design Considerations and Best Practices:
  • Pankaj emphasized the importance of design considerations and best practices for integrating SAP with Power Platform, covering topics like custom connectors, middleware requirements, and high availability.
    • Custom Connectors: Pankaj highlighted the use of custom connectors in the integration process, explaining their role and importance in connecting SAP with Power Platform.
    • Middleware Requirements: Pankaj discussed the middleware requirements for the integration, including the placement of on-premise data gateways and the use of API management for secure connections.
    • High Availability: Pankaj emphasized the need for high availability in the integration, discussing strategies like load balancing and redundancy to ensure continuous operation.
  • Extending SAP Landing Zone:
  • Pankaj explained how to extend the SAP landing zone with Power Platform components, detailing the placement of connectors and on-premise data gateways in different scenarios.
    • Extending Landing Zone: Pankaj explained the process of extending the SAP landing zone with Power Platform components, detailing the placement of connectors and on-premise data gateways in various scenarios.
    • Connector Placement: Pankaj provided specific details on where to place connectors within the SAP landing zone, depending on whether the SAP system is on-premise, on Azure, or on another cloud provider.
  • Security and Single Sign-On:
  • Pankaj discussed the importance of security and single sign-on (SSO) in SAP and Power Platform integration, highlighting the use of Azure API management and Microsoft Entra ID for secure connections.
    • Security Importance: Pankaj emphasized the critical role of security in the integration of SAP with Power Platform, ensuring that all connections are secure and compliant with standards.
    • Single Sign-On: Pankaj highlighted the use of single sign-on (SSO) for secure connections, explaining how Azure API management and Microsoft Entra ID facilitate SSO in the integration process.
  • Living Document and Continuous Updates:
  • Holger and Pankaj emphasized that the SAP on Azure Landing Zone accelerator is a living document, continuously updated based on customer feedback, new capabilities, and changes in products and services.
    • Living Document: Holger and Pankaj emphasized that the SAP on Azure Landing Zone accelerator is a living document, continuously updated to reflect new capabilities, customer feedback, and changes in products and services.
    • Continuous Updates: Pankaj explained that the document is regularly updated to incorporate new learnings, product changes, and customer feedback, ensuring it remains relevant and useful.