You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/innovate-rise-sap-microsoft-cloud/includes/2-sap-with-microsoft-cloud.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ As the project manager for a manufacturer, you utilize RISE with SAP on Microsof
8
8
9
9
There are a range of SAP deployment options for combining with Microsoft Cloud:
10
10
11
-
-**RISE with SAP**: An SAP fully managed service that handles all underlying infrastructure, enabling businesses to concentrate on their core operations. When RISE with SAP is deployed in Azure, SAP owns and manages the Azure tenent and SAP services.
11
+
-**RISE with SAP**: An SAP fully managed service that handles all underlying infrastructure, enabling businesses to concentrate on their core operations. When RISE with SAP is deployed in Azure, SAP owns and manages the Azure tenant and SAP services.
12
12
-**Customer managed VMs on Azure**: Businesses retain greater control over their SAP systems by managing their own virtual machines (VMs) on Azure. SAP on Azure VMs is a solution for businesses with specific customization needs or those desiring more hands-on control.
13
13
-**On-premises**: Host SAP applications on the business's own infrastructure for maximum control and customization. Ideal for organizations with strict data security needs or existing on-premises investments, and supports businesses still migrating to cloud VMs or RISE with SAP.
14
14
@@ -18,7 +18,7 @@ The following Microsoft integration architecture example for SAP apples to RISE
18
18
19
19
The following diagram shows the traffic flow from Power Platform and Copilot to SAP through Azure API Management:
20
20
21
-
:::image type="content" source="../media/traffic-flow.jpg" alt-text="Diagram that shows the traffic flow from Power Platform and Copilot to SAP through Azure API Management." lightbox="../media/entra-id-apim-oauth/traffic-flow.jpg":::
21
+
:::image type="content" source="../media/traffic-flow.jpg" alt-text="Diagram that shows the traffic flow from Power Platform and Copilot to SAP through Azure API Management." lightbox="../media/traffic-flow.jpg":::
22
22
23
23
## Describe the key features of RISE with SAP on Microsoft Cloud
24
24
@@ -35,9 +35,9 @@ RISE with SAP on Microsoft Cloud provides a robust platform for businesses to ru
35
35
36
36
Azure services play a crucial role in supporting and enhancing the functionality of RISE with SAP. Key integration points include:
37
37
38
-
-**Network connectivity**: Azure provides network connectivity options to ensure seamless communication between SAP systems and other applications. Both virtual network peering and VPN connections can be used to connect the customer's Azure tenant to the SAP Azure tenant. These methods exist in practice and are used to ensure secure and efficient communication between the two environments. The chosen solution depends on the customer's requirements, existing infrastructure, and support levels by SAP. SAP owns the Azure tenet when RISE with SAP runs on Azure.
39
-
-**Identity management**: Microsoft Entra ID serves as the primary identity provider, managing user authentication and authorization for SAP applications and services. It enables single sign-on (SSO), allowing users to access multiple SAP services with a single set of credentials, simplifying the user experience and enhancing security. SAP Cloud Identity Services acts as a proxy identity provider, with Entra ID configured as the leading identity provider. SAP Cloud Identity Services is added as a trusted application in Entra ID, and all SAP applications and services are configured in the SAP Cloud Identity Services management console. Entra ID also supports automated user provisioning, ensuring that new employees' user accounts are automatically created in SAP applications for seamless access and management.
40
-
-**Identity Security**: Entra ID offers robust security features like multifactor authentication (MFA) and conditional access policies to protect user identities and ensure compliance. For SAP applications, principal propagation is used for SSO, allowing SAP Cloud Identity Authentication Services to act as a proxy identity provider, forwarding authentication requests to Entra ID.
38
+
-**Network connectivity**: Azure provides network connectivity options to ensure seamless communication between SAP systems and other applications. Both virtual network peering and VPN connections can be used to connect the customer's Azure tenant to the SAP Azure tenant. These methods exist in practice and are used to ensure secure and efficient communication between the two environments. The chosen solution depends on the customer's requirements, existing infrastructure, and support levels by SAP. SAP owns the Azure tenant when RISE with SAP runs on Azure.
39
+
-**Identity management**: Microsoft Entra ID serves as the primary identity provider, managing user authentication and authorization for SAP applications and services. It enables single sign-on (SSO), allowing users to access multiple SAP services with a single set of credentials, simplifying the user experience and enhancing security. SAP Cloud Identity Services acts as a proxy identity provider, with Microsoft Entra ID configured as the leading identity provider. SAP Cloud Identity Services is added as a trusted application in Microsoft Entra ID, and all SAP applications and services are configured in the SAP Cloud Identity Services management console. Microsoft Entra ID also supports automated user provisioning, ensuring that new employees' user accounts are automatically created in SAP applications for seamless access and management.
40
+
-**Identity Security**: Microsoft Entra ID offers robust security features like multifactor authentication (MFA) and conditional access policies to protect user identities and ensure compliance. For SAP applications, principal propagation is used for SSO, allowing SAP Cloud Identity Authentication Services to act as a proxy identity provider, forwarding authentication requests to Microsoft Entra ID.
41
41
-**Data Services**: Azure Data Factory, Synapse, and Power BI enable advanced data analytics and reporting for SAP integration and SAP RISE environments. These tools facilitate seamless data movement, transformation, and visualization, providing valuable insights and enhancing decision-making processes.
42
42
-**Disaster Recovery and Backup**: With Azure Site Recovery and Azure Backup services, robust disaster recovery and backup capabilities are provided for the customer's Azure resources that integrate with RISE with SAP. While SAP controls the platform, these services ensure that the surrounding Azure resources are protected and compliant.
43
43
-**AI and machine learning**: Integration of Azure AI and Machine Learning services with SAP drives intelligent decision-making and process automation.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/innovate-rise-sap-microsoft-cloud/includes/3-leverage-ai-optimize-sap-workflows-microsoft-teams.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,24 +16,24 @@ The diagram illustrates a sample architecture for integrating Microsoft Power Pl
16
16
Diagram that shows an architecture of a Microsoft Power Platform integration with a typical SAP landing zone.
17
17
:::image-end:::
18
18
19
-
### Power Platform Environment
19
+
### Power Platform environment
20
20
21
21
- Contains Power BI, Power Apps, Power Pages, and Copilot Studio, all connected to Power Automate.
22
22
- Power Automate connects to SAP ERP connector, OData connector, and a custom connector.
23
23
- Connects to a Microsoft Entra tenant.
24
24
25
-
### Data Flow
25
+
### Data flow
26
26
27
27
- Data from Power BI and SAP ERP connector passes through a firewall to the SAP environment.
28
28
- Data from OData and custom connectors goes through an API gateway into the SAP environment.
29
29
30
-
### SAP Environment
30
+
### SAP environment
31
31
32
32
- Contains an on-premises data gateway, receiving data from the firewall.
33
33
- Shows data flows from the gateway to SAP .NET Connector.
34
34
- Includes OData API, REST/SOAP API, and HANA SQL port for data flow from the API gateway into SAP.
35
35
36
-
### Client Applications Box
36
+
### Client applications box
37
37
38
38
- Data flows from laptop, mobile device, Power Automate desktop, SAP GUI, and Power BI Desktop.
39
39
- Data from Power BI Desktop flows to SAP .NET Connector and SAP HANA ODBC driver.
0 commit comments