Merge pull request #227140 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 2/13

Author: ttorble

articles/active-directory/saas-apps/agiloft-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 01/09/2023
+ms.date: 02/10/2023
 ms.author: jeedes
 ---
 # Tutorial: Azure Active Directory integration with Agiloft Contract Management Suite
@@ -85,11 +85,11 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 5. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
 
-    In the **Sign-on URL** text box, type the URL:
-    `https://www.agiloft.com`
+    In the **Sign-on URL** text box, type a URL using the following pattern:
+    `https://<SUBDOMAIN>.agiloft.com:443/gui2/samlssologin.jsp?project=<KB_NAME>`
 
     > [!NOTE]
-    > These values are not real. Update these values with the actual Identifier and Reply URL. Contact [Agiloft Contract Management Suite Client support team](https://www.agiloft.com/support-login.htm) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+    > These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [Agiloft Contract Management Suite Client support team](https://www.agiloft.com/support-login.htm) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
 6. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Certificate (Base64)** from the given options as per your requirement and save it on your computer.
 

articles/active-directory/saas-apps/oracle-idcs-for-ebs-tutorial.md

@@ -0,0 +1,108 @@
+---
+title: Azure Active Directory SSO integration with Oracle IDCS for E-Business Suite
+description: Learn how to configure single sign-on between Azure Active Directory and Oracle IDCS for E-Business Suite.
+services: active-directory
+author: jeevansd
+manager: CelesteDG
+ms.reviewer: CelesteDG
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: how-to
+ms.date: 02/07/2023
+ms.author: jeedes
+
+---
+
+# Azure Active Directory SSO integration with Oracle IDCS for E-Business Suite
+
+In this article, you'll learn how to integrate Oracle IDCS for E-Business Suite with Azure Active Directory (Azure AD). When you integrate Oracle IDCS for E-Business Suite with Azure AD, you can:
+
+* Control in Azure AD who has access to Oracle IDCS for E-Business Suite.
+* Enable your users to be automatically signed-in to Oracle IDCS for E-Business Suite with their Azure AD accounts.
+* Manage your accounts in one central location - the Azure portal.
+
+You'll configure and test Azure AD single sign-on for Oracle IDCS for E-Business Suite in a test environment. Oracle IDCS for E-Business Suite supports only **SP** initiated single sign-on.
+
+> [!NOTE]
+> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
+
+## Prerequisites
+
+To integrate Azure Active Directory with Oracle IDCS for E-Business Suite, you need:
+
+* An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+* One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
+* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* Oracle IDCS for E-Business Suite single sign-on (SSO) enabled subscription.
+
+## Add application and assign a test user
+
+Before you begin the process of configuring single sign-on, you need to add the Oracle IDCS for E-Business Suite application from the Azure AD gallery. You need a test user account to assign to the application and test the single sign-on configuration.
+
+### Add Oracle IDCS for E-Business Suite from the Azure AD gallery
+
+Add Oracle IDCS for E-Business Suite from the Azure AD application gallery to configure single sign-on with Oracle IDCS for E-Business Suite. For more information on how to add application from the gallery, see the [Quickstart: Add application from the gallery](../manage-apps/add-application-portal.md).
+
+### Create and assign Azure AD test user
+
+Follow the guidelines in the [create and assign a user account](../manage-apps/add-application-portal-assign-users.md) article to create a test user account in the Azure portal called B.Simon.
+
+Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, and assign roles. The wizard also provides a link to the single sign-on configuration pane in the Azure portal. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides). 
+
+## Configure Azure AD SSO
+
+Complete the following steps to enable Azure AD single sign-on in the Azure portal.
+
+1. In the Azure portal, on the **Oracle IDCS for E-Business Suite** application integration page, find the **Manage** section and select **single sign-on**.
+1. On the **Select a single sign-on method** page, select **SAML**.
+1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings.
+
+   ![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
+
+1. On the **Basic SAML Configuration** section, perform the following steps:
+
+    a. In the **Identifier** textbox, type a URL using the following pattern: ` https://<SUBDOMAIN>.oraclecloud.com/`
+
+    b. In the **Reply URL** textbox, type a URL using the following pattern: `https://<SUBDOMAIN>.oraclecloud.com/v1/saml/<UNIQUEID>`
+
+    c. In the **Sign on URL** textbox, type a URL using the following pattern:
+    ` https://<SUBDOMAIN>.oraclecloud.com/`
+    
+    >[!NOTE]
+    > These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [Oracle IDCS for E-Business Suite support team](https://www.oracle.com/support/advanced-customer-services/) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+
+1. Your Oracle IDCS for E-Business Suite application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows an example for this. The default value of **Unique User Identifier** is **user.userprincipalname** but Oracle IDCS for E-Business Suite expects this to be mapped with the user's email address. For that you can use **user.mail** attribute from the list or use the appropriate attribute value based on your organization configuration.
+
+	![image](common/default-attributes.png)
+
+1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section,  find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
+
+	![The Certificate download link](common/metadataxml.png)
+
+## Configure Oracle IDCS for E-Business Suite SSO
+
+To configure single sign-on on Oracle IDCS for E-Business Suite side, you need to send the downloaded Federation Metadata XML file from Azure portal to [Oracle IDCS for E-Business Suite support team](https://www.oracle.com/support/advanced-customer-services/). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create Oracle IDCS for E-Business Suite test user
+
+In this section, you create a user called Britta Simon at Oracle IDCS for E-Business Suite. Work with [Oracle IDCS for E-Business Suite support team](https://www.oracle.com/support/advanced-customer-services/) to add the users in the Oracle IDCS for E-Business Suite platform. Users must be created and activated before you use single sign-on.
+
+## Test SSO 
+
+In this section, you test your Azure AD single sign-on configuration with following options. 
+
+* Click on **Test this application** in Azure portal. This will redirect to Oracle IDCS for E-Business Suite Sign-on URL where you can initiate the login flow. 
+
+* Go to Oracle IDCS for E-Business Suite Sign-on URL directly and initiate the login flow from there.
+
+* You can use Microsoft My Apps. When you select the Oracle IDCS for E-Business Suite tile in the My Apps, this will redirect to Oracle IDCS for E-Business Suite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
+
+## Additional resources
+
+* [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+* [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
+
+## Next steps
+
+Once you configure Oracle IDCS for E-Business Suite you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](/cloud-app-security/proxy-deployment-aad).

articles/active-directory/saas-apps/toc.yml

@@ -1727,6 +1727,8 @@
         href: oracle-cloud-tutorial.md
       - name: Oracle Fusion ERP
         href: oracle-fusion-erp-tutorial.md
+      - name: Oracle IDCS for E-Business Suite
+        href: oracle-idcs-for-ebs-tutorial.md
       - name: Oracle IDCS for PeopleSoft
         href: oracle-idcs-for-peoplesoft-tutorial.md 
       - name: OrgChart Now

articles/app-service/configure-vnet-integration-enable.md

@@ -5,27 +5,24 @@ keywords: vnet integration
 author: madsd
 ms.author: madsd
 ms.topic: how-to
-ms.date: 10/20/2021
+ms.date: 02/13/2023
 ms.tool: azure-cli, azure-powershell
 ---
 
 # Enable virtual network integration in Azure App Service
 
-Through integrating with an Azure virtual network (VNet) from your [Azure App Service app](./overview.md), you can reach private resources from your app within the virtual network. The VNet integration feature has two variations:
-
-* **Regional virtual network integration**: Connect to Azure virtual networks in the same region. You must have a dedicated subnet in the virtual network you're integrating with.
-* **Gateway-required virtual network integration**: When you connect directly to a virtual network in other regions or to a classic virtual network in the same region, you must use gateway-required virtual network integration.
-
-This article describes how to set up regional virtual network integration.
+Through integrating with an Azure virtual network from your [Azure App Service app](./overview.md), you can reach private resources from your app within the virtual network.
 
 ## Prerequisites
 
-The VNet integration feature requires:
+The virtual network integration feature requires:
 
 - An App Service pricing tier [that supports virtual network integration](./overview-vnet-integration.md).
 - A virtual network in the same region with an empty subnet.
 
-The subnet must be delegated to Microsoft.Web/serverFarms. If the delegation isn't done before integration, the provisioning process will configure this delegation. The subnet must be allocated an IPv4 `/28` block (16 addresses). We recommend that you have a minimum of 64 addresses (IPv4 `/26` block) to allow for maximum horizontal scale.
+The subnet must be delegated to Microsoft.Web/serverFarms. If the delegation isn't done before integration, the provisioning process configures this delegation. The subnet must be allocated an IPv4 `/28` block (16 addresses). We recommend that you have a minimum of 64 addresses (IPv4 `/26` block) to allow for maximum horizontal scale.
+
+If the virtual network is in a different subscription than the app, you must ensure that the subscription with the virtual network is registered for the `Microsoft.Web` resource provider. You can explicitly register the provider [by following this documentation](../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider), but it's automatically registered when creating the first web app in a subscription.
 
 ## Configure in the Azure portal
 
@@ -39,7 +36,7 @@ The subnet must be delegated to Microsoft.Web/serverFarms. If the delegation isn
 
     :::image type="content" source="./media/configure-vnet-integration-enable/vnetint-add-vnet.png" alt-text="Screenshot that shows selecting the virtual network.":::
 
-During the integration, your app is restarted. When integration is finished, you'll see details on the virtual network you're integrated with.
+During the integration, your app is restarted. When integration is finished, you see details on the virtual network you're integrated with.
 
 ## Configure with the Azure CLI
 
@@ -50,7 +47,7 @@ az webapp vnet-integration add --resource-group <group-name> --name <app-name> -
 ```
 
 > [!NOTE]
-> The command checks if the subnet is delegated to Microsoft.Web/serverFarms and applies the necessary delegation if it isn't configured. If the subnet was configured, and you don't have permissions to check it, or if the virtual network is in another subscription, you can use the *--skip-delegation-check* parameter to bypass the validation.
+> The command checks if the subnet is delegated to Microsoft.Web/serverFarms and applies the necessary delegation if it isn't configured. If the subnet was configured, and you don't have permissions to check it, or if the virtual network is in another subscription, you can use the `--skip-delegation-check` parameter to bypass the validation.
 
 ## Configure with Azure PowerShell
 
@@ -83,7 +80,7 @@ $subnet = Add-AzDelegation -Name "myDelegation" -ServiceName "Microsoft.Web/serv
 Set-AzVirtualNetwork -VirtualNetwork $vnet
 ```
 
-Configure VNet Integration.
+Configure virtual network integration.
 
 > [!NOTE]
 > If the webapp is in another subscription than virtual network, you can use the *Set-AzContext -Subscription "xxxx-xxxx-xxxx-xxxx"* command to set the current subscription context. Set the current subscription context to the subscription where the web app was deployed.