Merge pull request #228205 from MicrosoftDocs/main

2/22 AM Publish

Author: huypub

articles/active-directory/develop/desktop-quickstart-portal-wpf.md

@@ -9,10 +9,12 @@ ms.subservice: develop
 ms.topic: quickstart
 ms.workload: identity
 ms.date: 08/18/2022
+ROBOTS: NOINDEX
 ms.author: owenrichards
 ms.custom: aaddev, identityplatformtop40, mode-api
 #Customer intent: As an application developer, I want to learn how my Windows Presentation Foundation (WPF) application can get an access token and call an API that's protected by the Microsoft identity platform.
 ---
+
 # Quickstart: Sign in users and call Microsoft Graph in a Windows desktop app
 
 > [!div renderon="docs"]
@@ -23,7 +25,7 @@ ms.custom: aaddev, identityplatformtop40, mode-api
 > We apologize for the inconvenience and appreciate your patience while we work to get this resolved.
 
 > [!div renderon="portal" id="display-on-portal" class="sxs-lookup"]
-> ## Quickstart: Acquire a token and call the Microsoft Graph API from a Windows desktop application
+> # Quickstart: Acquire a token and call the Microsoft Graph API from a Windows desktop application
 >
 > In this quickstart, you download and run a code sample that demonstrates how a Windows Presentation Foundation (WPF) application can sign in users and get an access token to call the Microsoft Graph API. 
 > 

articles/active-directory/fundamentals/road-to-the-cloud-posture.md

@@ -114,7 +114,7 @@ In this state:
 
 * A plan to move apps that depend on Active Directory and are part of the vision for the future-state Azure AD environment is being executed. A plan to replace services that won't move (file, print, or fax services) is in place.
 
-* On-premises workloads have been replaced with cloud alternatives such as Windows Virtual Desktop, Azure Files, or Google Cloud Print. Azure SQL Managed Instance replaces SQL Server.
+* On-premises workloads have been replaced with cloud alternatives such as Windows Virtual Desktop, Azure Files, or Universal Print. Azure SQL Managed Instance replaces SQL Server.
 
 ### State 5: 100% cloud
 

articles/active-directory/fundamentals/whats-new.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: multi-tenant-organizations
 ms.topic: overview
-ms.date: 02/13/2023
+ms.date: 02/22/2023
 ms.author: rolyon
 ms.custom: it-pro
 
@@ -123,7 +123,7 @@ For anyone that has used Azure AD to [provision identities into a SaaS applicati
 
 In the source tenant: Using this feature requires Azure AD Premium P1 licenses. Each user who is synchronized with cross-tenant synchronization must have a P1 license in their home/source tenant. To find the right license for your requirements, see [Compare generally available features of Azure AD](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
 
-In the target tenant: Cross-tenant sync relies on the Azure AD External Identities billing model. To understand the external identities licensing model, see [MAU billing model for Azure AD External Identities](../external-identities/external-identities-pricing.md)
+In the target tenant: Cross-tenant sync relies on the Azure AD External Identities billing model. To understand the external identities licensing model, see [MAU billing model for Azure AD External Identities](../external-identities/external-identities-pricing.md). You will also need at least one Azure AD Premium P1 license in the target tenant to enable auto-redemption. 
 
 ## Frequently asked questions
 

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-overview.md

@@ -142,6 +142,9 @@ This section guides you through the steps to configure the Azure AD provisioning
     |urn:ietf:params:scim:schemas:oracle:idcs:extension:user:User:bypassNotification|Boolean|
     |urn:ietf:params:scim:schemas:oracle:idcs:extension:user:User:isFederatedUser|Boolean|
 
+> [!NOTE]
+> Additional extension attributes must begin with "urn:ietf:params:scim:api:"
+
 10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Oracle Cloud Infrastructure Console**.
 
 11. Review the group attributes that are synchronized from Azure AD to Oracle Cloud Infrastructure Console in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Oracle Cloud Infrastructure Console for update operations. Select the **Save** button to commit any changes.

articles/active-directory/saas-apps/oracle-cloud-infrastructure-console-provisioning-tutorial.md

@@ -2661,6 +2661,8 @@
         href: whos-on-location-tutorial.md
       - name: Wikispaces
         href: wikispaces-tutorial.md
+      - name: Windchill
+        href: windchill-tutorial.md
       - name: Wingspan eTMF
         href: wingspanetmf-tutorial.md
       - name: WireWheel

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

@@ -0,0 +1,112 @@
+---
+title: Azure Active Directory SSO integration with Windchill
+description: Learn how to configure single sign-on between Azure Active Directory and Windchill.
+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/22/2023
+ms.author: jeedes
+
+---
+
+# Azure Active Directory SSO integration with Windchill
+
+In this article, you'll learn how to integrate Windchill with Azure Active Directory (Azure AD). Windchill PLM Software - Realize value quickly with out-of-the-box functionality across a comprehensive portfolio of core Product Data Management and advanced Product Lifecycle Management applications. When you integrate Windchill with Azure AD, you can:
+
+* Control in Azure AD who has access to Windchill.
+* Enable your users to be automatically signed-in to Windchill 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 Windchill in a test environment. Windchill supports **SP** and **IDP** 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 Windchill, 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/).
+* Windchill 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 Windchill 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 Windchill from the Azure AD gallery
+
+Add Windchill from the Azure AD application gallery to configure single sign-on with Windchill. 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 **Windchill** 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, the user does not have to perform any step as the app is already pre-integrated with Azure.
+
+1. If you wish to configure the application in **SP** initiated mode, then perform the following step:
+
+    In the **Sign on URL** textbox, type a URL using the following pattern:
+    `https://<hostname:port>/Shibboleth.sso/Login`
+
+    > [!NOTE]
+    > This value is not real. Update this value with the actual Sign on URL. Contact [Windchill Client support team](mailto:[email protected]) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
+
+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.
+
+    ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
+
+1. On the **Set up Windchill** section, copy the appropriate URL(s) based on your requirement.
+
+	![Screenshot shows to copy configuration appropriate URL.](common/copy-configuration-urls.png "Metadata")
+
+## Configure Windchill SSO
+
+To configure single sign-on on **Windchill** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Windchill support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+
+### Create Windchill test user
+
+In this section, you create a user called Britta Simon at Windchill. Work with [Windchill support team](mailto:[email protected]) to add the users in the Windchill 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. 
+
+#### SP initiated:
+
+1. Click on **Test this application** in Azure portal. This will redirect to Windchill Sign-on URL where you can initiate the login flow.  
+
+1. Go to Windchill Sign-on URL directly and initiate the login flow from there.
+
+#### IDP initiated:
+
+1. Click on **Test this application** in Azure portal and you should be automatically signed in to the Windchill for which you set up the SSO. 
+
+1. You can also use Microsoft My Apps to test the application in any mode. When you click the Windchill tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Windchill for which you set up the SSO. 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 Windchill 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).