Merge pull request #217509 from v-hgampala/broken-links-fixing

prmerger-automator[bot] · web-flow · commit a28bc02d95a4 · 2022-11-08T04:42:11.000Z
Product Backlog Item 2157610: SaaS App Tutorial: Fixing Broken links …
diff --git a/articles/active-directory/saas-apps/invision-provisioning-tutorial.md b/articles/active-directory/saas-apps/invision-provisioning-tutorial.md
@@ -13,7 +13,7 @@ ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.tgt_pltfrm: na
 ms.topic: tutorial
-ms.date: 06/25/2020
+ms.date: 11/08/2022
 ms.author: thwimmer
 ---
 
@@ -35,7 +35,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 * [An Azure AD tenant](../develop/quickstart-create-new-tenant.md) 
 * A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
-* An [InVision Enterprise account](https://www.invisionapp.com/enterprise) with SSO enabled.
+* An [InVision Enterprise account](https://www.invisionapp.com/) with SSO enabled.
 * A user account in InVision with Admin permissions.
 
 ## Step 1. Plan your provisioning deployment
@@ -45,7 +45,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 ## Step 2. Configure InVision to support provisioning with Azure AD
 
-1. Sign in to your [InVision Enterprise account](https://www.invisionapp.com/enterprise) as an Admin or Owner. Open the **Team Settings** drawer on the bottom left and select **Settings**.
+1. Sign in to your [InVision Enterprise account](https://www.invisionapp.com/) as an Admin or Owner. Open the **Team Settings** drawer on the bottom left and select **Settings**.
 
    ![SCIM setup configuration](./media/invision-provisioning-tutorial/invision-scim-settings.png)
 
diff --git a/articles/active-directory/saas-apps/juno-journey-provisioning-tutorial.md b/articles/active-directory/saas-apps/juno-journey-provisioning-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 04/16/2020
+ms.date: 11/08/2022
 ms.author: thwimmer
 ---
 
@@ -31,7 +31,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 * [An Azure AD tenant](../develop/quickstart-create-new-tenant.md) 
 * A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
-*  A [Juno Journey tenant](https://www.junojourney.com/getstarted).
+*  A [Juno Journey tenant](https://app.junojourney.com/login).
 *  A user account in Juno Journey with Admin permissions.
 
 ## Step 1. Plan your provisioning deployment
diff --git a/articles/active-directory/saas-apps/mobilexpense-tutorial.md b/articles/active-directory/saas-apps/mobilexpense-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 06/29/2022
+ms.date: 11/08/2022
 ms.author: jeedes
 ---
 # Tutorial: Azure AD SSO integration with Mobile Xpense
@@ -88,7 +88,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
     `https://<sub-domain>.mobilexpense.com/<customername>`
 
 	> [!NOTE]
-	> These values are not real. Update these values with the actual Reply URL and Sign-on URL. Contact [Mobile Xpense Client support team](https://www.mobilexpense.net/contact) 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 Reply URL and Sign-on URL. Contact [Mobile Xpense Client support team](https://www.mobilexpense.com/contact) to get these values. 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, click **Download** to download the **Federation Metadata XML** from the given options as per your requirement and save it on your computer.
 
@@ -124,11 +124,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ## Configure Mobile Xpense SSO
 
-To configure single sign-on on **Mobile Xpense** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Mobile Xpense support team](https://www.mobilexpense.net/contact). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on **Mobile Xpense** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Mobile Xpense support team](https://www.mobilexpense.com/contact). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create Mobile Xpense test user
 
-In this section, you create a user called Britta Simon in Mobile Xpense. Work with [Mobile Xpense support team](https://www.mobilexpense.net/contact) to add the users in the Mobile Xpense platform. Users must be created and activated before you use single sign-on.
+In this section, you create a user called Britta Simon in Mobile Xpense. Work with [Mobile Xpense support team](https://www.mobilexpense.com/contact) to add the users in the Mobile Xpense platform. Users must be created and activated before you use single sign-on.
 
 ## Test SSO 
 
diff --git a/articles/active-directory/saas-apps/predictixpricereporting-tutorial.md b/articles/active-directory/saas-apps/predictixpricereporting-tutorial.md
@@ -84,7 +84,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
      `https://<companyname-pricing>.predictix.com/sso/request`
 
 	> [!NOTE]
-	> These values are placeholders. Update these values with the actual Identifier and Sign on URL. Contact the [Predictix Price Reporting support team](https://www.infor.com/company/customer-center/) to get the values. You can also refer to the patterns shown in the **Basic SAML Configuration** dialog box in the Azure portal.
+	> These values are placeholders. Update these values with the actual Identifier and Sign on URL. Contact the [Predictix Price Reporting support team](https://www.infor.com/customer-center) to get the values. You can also refer to the patterns shown in the **Basic SAML Configuration** dialog box in the Azure portal.
 
 5. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, select the **Download** link next to **Certificate (Base64)**, per your requirements, and save the certificate on your computer:
 
@@ -120,11 +120,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
 
 ## Configure Predictix Price Reporting SSO
 
-To configure single sign-on on the Predictix Price Reporting side, you need to send the certificate that you downloaded and the URLs that you copied from the Azure portal to the [Predictix Price Reporting support team](https://www.infor.com/company/customer-center/). This team ensures the SAML SSO connection is set properly on both sides.
+To configure single sign-on on the Predictix Price Reporting side, you need to send the certificate that you downloaded and the URLs that you copied from the Azure portal to the [Predictix Price Reporting support team](https://www.infor.com/customer-center). This team ensures the SAML SSO connection is set properly on both sides.
 
 ### Create a Predictix Price Reporting test user
 
-Next, you need to create a user named Britta Simon in Predictix Price Reporting. Work with the [Predictix Price Reporting support team](https://www.infor.com/company/customer-center/) to add users. Users need to be created and activated before you use single sign-on.
+Next, you need to create a user named Britta Simon in Predictix Price Reporting. Work with the [Predictix Price Reporting support team](https://www.infor.com/customer-center) to add users. Users need to be created and activated before you use single sign-on.
 
 ## Test SSO
 
diff --git a/articles/active-directory/saas-apps/zendesk-provisioning-tutorial.md b/articles/active-directory/saas-apps/zendesk-provisioning-tutorial.md
@@ -46,7 +46,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 ## Step 2. Configure Zendesk to support provisioning with Azure AD
 
-1. Log in to [Admin Center](https://support.zendesk.com/hc/en-us/articles/4408839227290#topic_hfg_dyz_1hb), click  **Apps and integrations** in the sidebar, then select **APIs > Zendesk APIs**.
+1. Log in to [Admin Center](https://support.zendesk.com/hc/en-us/articles/4581766374554#topic_hfg_dyz_1hb), click  **Apps and integrations** in the sidebar, then select **APIs > Zendesk APIs**.
 1. Click the **Settings** tab, and make sure Token Access is **enabled**.
 1. Click the **Add API token** button to the right of **Active API Tokens**.The token is generated and displayed.
 1. Enter an **API token description**.
