Skip to content

Commit fa46f0f

Browse files
authored
Merge pull request #236252 from MicrosoftDocs/main
Merge main to live, 4 AM
2 parents 224de9b + 206960f commit fa46f0f

File tree

130 files changed

+2567
-1151
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

130 files changed

+2567
-1151
lines changed

.openpublishing.redirection.healthcare-apis.json

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -594,15 +594,27 @@
594594
"redirect_document_id": false
595595
},
596596
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-config.md",
597-
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-config",
597+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-portal",
598598
"redirect_document_id": false
599599
},
600600
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-deploy.md",
601-
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-post",
601+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-portal",
602602
"redirect_document_id": false
603603
},
604604
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-manual.md",
605-
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-prerequisites",
605+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-portal",
606+
"redirect_document_id": false
607+
},
608+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-manual-prerequisites.md",
609+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-portal",
610+
"redirect_document_id": false
611+
},
612+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-manual-config.md",
613+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-portal",
614+
"redirect_document_id": false
615+
},
616+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-manual-post.md",
617+
"redirect_url": "/azure/healthcare-apis/iot/deploy-manual-portal",
606618
"redirect_document_id": false
607619
},
608620
{ "source_path_from_root": "/articles/healthcare-apis/iot/iot-connector-overview.md",

articles/active-directory/app-provisioning/sap-successfactors-integration-reference.md

Lines changed: 37 additions & 49 deletions
Large diffs are not rendered by default.

articles/active-directory/develop/app-objects-and-service-principals.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: conceptual
1111
ms.workload: identity
12-
ms.date: 12/14/2022
12+
ms.date: 04/27/2023
1313
ms.author: ryanwi
1414
ms.custom: contperf-fy21q4-portal, aaddev, identityplatformtop40
1515
ms.reviewer: sureshja

articles/active-directory/develop/howto-configure-publisher-domain.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: how-to
1111
ms.workload: identity
12-
ms.date: 01/05/2023
12+
ms.date: 04/27/2023
1313
ms.author: owenrichards
14-
ms.reviewer: xurobert, brianokoyo
14+
ms.reviewer: xurobert
1515
ms.custom: contperf-fy21q4, aaddev
1616
---
1717

articles/active-directory/develop/mark-app-as-publisher-verified.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.workload: identity
1111
ms.date: 03/16/2023
1212
ms.author: ryanwi
1313
ms.custom: aaddev
14-
ms.reviewer: xurobert, brianokoyo, ardhanap
14+
ms.reviewer: xurobert
1515
---
1616

1717
# Mark your app as publisher verified

articles/active-directory/develop/publisher-verification-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,10 @@ ms.service: active-directory
88
ms.subservice: develop
99
ms.topic: conceptual
1010
ms.workload: identity
11-
ms.date: 11/09/2022
11+
ms.date: 04/27/2023
1212
ms.author: ryanwi
1313
ms.custom: aaddev
14-
ms.reviewer: ardhanap, brianokoyo, jesakowi
14+
ms.reviewer: xurobert
1515
---
1616

1717
# Publisher verification

articles/active-directory/develop/troubleshoot-publisher-verification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.workload: identity
1111
ms.date: 03/16/2023
1212
ms.author: ryanwi
1313
ms.custom: aaddev
14-
ms.reviewer: ardhanap, jesakowi
14+
ms.reviewer: xurobert
1515
---
1616

1717
# Troubleshoot publisher verification

articles/active-directory/external-identities/whats-new-docs.md

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory External Identities"
33
description: "New and updated documentation for the Azure Active Directory External Identities."
4-
ms.date: 03/31/2023
4+
ms.date: 04/28/2023
55
ms.service: active-directory
66
ms.subservice: B2B
77
ms.topic: reference
@@ -15,6 +15,15 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory External Identities documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the External Identities service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
1717

18+
## April 2023
19+
20+
### Updated articles
21+
22+
- [Allow or block domains](allow-deny-list.md) Screenshots were updated.
23+
- [Authentication and Conditional Access](authentication-conditional-access.md) Links to other articles were updated.
24+
- [Code and Azure PowerShell samples](code-samples.md) Minor text updates.
25+
- [Azure Active Directory](azure-ad-account.md) Minor text updates.
26+
1827
## March 2023
1928

2029
### Updated articles
@@ -35,15 +44,3 @@ Welcome to what's new in Azure Active Directory External Identities documentatio
3544
- [Azure Active Directory External Identities: What's new](whats-new-docs.md)
3645
- [Authentication and Conditional Access for External Identities](authentication-conditional-access.md)
3746
- [Quickstart: Add a guest user with PowerShell](b2b-quickstart-invite-powershell.md)
38-
39-
## January 2023
40-
41-
### Updated articles
42-
43-
- [Federation with SAML/WS-Fed identity providers for guest users](direct-federation.md)
44-
- [Add a self-service sign-up user flow to an app](self-service-sign-up-user-flow.md)
45-
- [Add a custom approval workflow to self-service sign-up](self-service-sign-up-add-approvals.md)
46-
- [Add Facebook as an identity provider for External Identities](facebook-federation.md)
47-
- [Leave an organization as an external user](leave-the-organization.md)
48-
- [External Identities in Azure Active Directory](external-identities-overview.md)
49-
- [External Identities documentation](index.yml)

articles/active-directory/reports-monitoring/howto-manage-inactive-user-accounts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The following details relate to the `lastSignInDateTime` property.
6161

6262
- Each interactive sign-in attempt results in an update of the underlying data store. Typically, sign-ins show up in the related sign-in report within 6 hours.
6363

64-
- To generate a `lastSignInDateTime` timestamp, you an attempted sign-in. The value of the `lastSignInDateTime` property may be blank if:
64+
- To generate a `lastSignInDateTime` timestamp, you must attempt a sign-in. Either a failed or successful sign-in attempt, as long as it is recorded in the [Azure AD sign-in logs](concept-all-sign-ins.md), will generate a `lastSignInDateTime` timestamp. The value of the `lastSignInDateTime` property may be blank if:
6565
- The last attempted sign-in of a user took place before April 2020.
6666
- The affected user account was never used for a sign-in attempt.
6767

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
---
2+
title: Azure Active Directory SSO integration with Alchemer
3+
description: Learn how to configure single sign-on between Azure Active Directory and Alchemer.
4+
services: active-directory
5+
author: jeevansd
6+
manager: CelesteDG
7+
ms.reviewer: CelesteDG
8+
ms.service: active-directory
9+
ms.subservice: saas-app-tutorial
10+
ms.workload: identity
11+
ms.topic: how-to
12+
ms.date: 04/27/2023
13+
ms.author: jeedes
14+
15+
---
16+
17+
# Azure Active Directory SSO integration with Alchemer
18+
19+
In this article, you learn how to integrate Alchemer with Azure Active Directory (Azure AD). Alchemer offers the world’s most flexible feedback and data collection platform that allows organizations to close the loop with their customers and employees quickly and effectively. When you integrate Alchemer with Azure AD, you can:
20+
21+
* Control in Azure AD who has access to Alchemer.
22+
* Enable your users to be automatically signed-in to Alchemer with their Azure AD accounts.
23+
* Manage your accounts in one central location - the Azure portal.
24+
25+
You configure and test Azure AD single sign-on for Alchemer in a test environment. Alchemer supports both **SP** and **IDP** initiated single sign-on and Just In Time user provisioning.
26+
27+
## Prerequisites
28+
29+
To integrate Azure Active Directory with Alchemer, you need:
30+
31+
* 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).
32+
* One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
33+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
34+
* Alchemer single sign-on (SSO) enabled subscription.
35+
36+
## Add application and assign a test user
37+
38+
Before you begin the process of configuring single sign-on, you need to add the Alchemer application from the Azure AD gallery. You need a test user account to assign to the application and test the single sign-on configuration.
39+
40+
### Add Alchemer from the Azure AD gallery
41+
42+
Add Alchemer from the Azure AD application gallery to configure single sign-on with Alchemer. 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).
43+
44+
### Create and assign Azure AD test user
45+
46+
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.
47+
48+
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).
49+
50+
## Configure Azure AD SSO
51+
52+
Complete the following steps to enable Azure AD single sign-on in the Azure portal.
53+
54+
1. In the Azure portal, on the **Alchemer** application integration page, find the **Manage** section and select **single sign-on**.
55+
1. On the **Select a single sign-on method** page, select **SAML**.
56+
1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings.
57+
58+
![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
59+
60+
1. On the **Basic SAML Configuration** section, perform the following steps:
61+
62+
a. In the **Identifier** textbox, type a URL using the following pattern:
63+
`https://app.alchemer.com/login/getsamlxml/idp/<INSTANCE>`
64+
65+
b. In the **Reply URL** textbox, type a URL using the following pattern:
66+
`https://app.alchemer.com/login/ssologin/idp/<INSTANCE>`
67+
68+
1. If you wish to configure the application in **SP** initiated mode, then perform the following step:
69+
70+
In the **Sign on URL** textbox, type a URL using the following pattern:
71+
`https://app.alchemer.com/login/initiatelogin/idp/<INSTANCE>`
72+
73+
> [!NOTE]
74+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [Alchemer Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
75+
76+
1. On the **Set-up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Raw)** and select **Download** to download the certificate and save it on your computer.
77+
78+
![Screenshot shows the Certificate download link.](common/certificateraw.png "Certificate")
79+
80+
1. On the **Set up Alchemer** section, copy the appropriate URL(s) based on your requirement.
81+
82+
![Screenshot shows to copy configuration appropriate URL.](common/copy-configuration-urls.png "Metadata")
83+
84+
## Configure Alchemer SSO
85+
86+
To configure single sign-on on **Alchemer** side, you need to send the downloaded **Certificate (Raw)** and appropriate copied URLs from Azure portal to [Alchemer support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
87+
88+
### Create Alchemer test user
89+
90+
In this section, a user called B.Simon is created in Alchemer. Alchemer supports just-in-time user provisioning, which is enabled by default. There's no action item for you in this section. If a user doesn't already exist in Alchemer, a new one is commonly created after authentication.
91+
92+
## Test SSO
93+
94+
In this section, you test your Azure AD single sign-on configuration with following options.
95+
96+
#### SP initiated:
97+
98+
* Click on **Test this application** in Azure portal. This will redirect to Alchemer Sign-on URL where you can initiate the login flow.
99+
100+
* Go to Alchemer Sign-on URL directly and initiate the login flow from there.
101+
102+
#### IDP initiated:
103+
104+
* Click on **Test this application** in Azure portal and you should be automatically signed in to the Alchemer for which you set up the SSO.
105+
106+
You can also use Microsoft My Apps to test the application in any mode. When you click the Alchemer 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 Alchemer 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).
107+
108+
## Additional resources
109+
110+
* [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
111+
* [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
112+
113+
## Next steps
114+
115+
Once you configure Alchemer 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).

0 commit comments

Comments
 (0)