Skip to content

Commit f25cd33

Browse files
committed
Merge branch 'main' of https://github.com/microsoftdocs/azure-docs-pr into phsm-support-guide
2 parents e271b81 + 3398e53 commit f25cd33

File tree

77 files changed

+624
-283
lines changed

Some content is hidden

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

77 files changed

+624
-283
lines changed

.openpublishing.publish.config.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1020,6 +1020,7 @@
10201020
"articles/load-testing/.openpublishing.redirection.azure-load-testing.json",
10211021
"articles/azure-video-indexer/.openpublishing.redirection.azure-video-indexer.json",
10221022
"articles/machine-learning/.openpublishing.redirection.machine-learning.json",
1023-
"articles/static-web-apps/.openpublishing.redirection.static-web-apps.json"
1023+
"articles/static-web-apps/.openpublishing.redirection.static-web-apps.json",
1024+
".openpublishing.redirection.virtual-desktop.json"
10241025
]
10251026
}

.openpublishing.redirection.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24728,11 +24728,6 @@
2472824728
"redirect_url": "/azure/traffic-manager/traffic-manager-manage-profiles",
2472924729
"redirect_document_id": false
2473024730
},
24731-
{
24732-
"source_path_from_root": "/articles/virtual-desktop/connect-windows-7-and-10.md",
24733-
"redirect_url": "/azure/virtual-desktop/connect-windows-7-10",
24734-
"redirect_document_id": true
24735-
},
2473624731
{
2473724732
"source_path_from_root": "/articles/troubleshoot-client-connection.md",
2473824733
"redirect_url": "/azure/virtual-desktop/troubleshoot-client",
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
{
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/virtual-desktop/connect-windows-7-and-10.md",
5+
"redirect_url": "/azure/virtual-desktop/connect-windows-7-10",
6+
"redirect_document_id": true
7+
}
8+
]
9+
}

articles/active-directory-b2c/azure-ad-external-identities-videos.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Get a deeper view into the features and technical aspects of the Azure AD B2C se
2929
|[Azure AD B2C sign-up sign-in](https://www.youtube.com/watch?v=c8rN1ZaR7wk&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=6&t=2s) 10:25 | [:::image type="icon" source="./media/external-identities-videos/customer-sign-up-sign-in.png" border="false":::](https://www.youtube.com/watch?v=c8rN1ZaR7wk&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=6) | [Azure AD B2C single sign on and self service password reset](https://www.youtube.com/watch?v=kRV-7PSLK38&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=7) 8:40 | [:::image type="icon" source="./media/external-identities-videos/single-sign-on.png" border="false":::](https://www.youtube.com/watch?v=kRV-7PSLK38&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=7) |
3030
| [Application and identity migration to Azure AD B2C](https://www.youtube.com/watch?v=Xw_YwSJmhIQ&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=9) 10:34 | [:::image type="icon" source="./media/external-identities-videos/identity-migration-aad-b2c.png" border="false":::](https://www.youtube.com/watch?v=Xw_YwSJmhIQ&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=9) | [Build resilient and scalable flows using Azure AD B2C](https://www.youtube.com/watch?v=8f_Ozpw9yTs&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=12) 16:47 | [:::image type="icon" source="./media/external-identities-videos/b2c-scalable-flows.png" border="false":::](https://www.youtube.com/watch?v=8f_Ozpw9yTs&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=12) |
3131
| [Building a custom CIAM solution with Azure AD B2C and ISV alliances](https://www.youtube.com/watch?v=UZjiGDD0wa8&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=8) 10:01 | [:::image type="icon" source="./media/external-identities-videos/build-custom-b2c-solution.png" border="false":::](https://www.youtube.com/watch?v=UZjiGDD0wa8&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=8) | [Protecting Web APIs with Azure AD B2C](https://www.youtube.com/watch?v=wuUu71RcsIo&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=10) 19:03 | [:::image type="icon" source="./media/external-identities-videos/protecting-web-apis.png" border="false":::](https://www.youtube.com/watch?v=wuUu71RcsIo&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=10) |
32-
| [Integration of SAML with Azure AD B2C](https://www.youtube.com/watch?v=r2TIVBCm7v4&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=11) 9:09 | [:::image type="icon" source="./media/external-identities-videos/saml-integration.png" border="false":::](https://www.youtube.com/watch?v=r2TIVBCm7v4&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=11) |
32+
| [Integration of SAML with Azure AD B2C](https://www.youtube.com/watch?v=r2TIVBCm7v4&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=11) 9:09 | [:::image type="icon" source="./media/external-identities-videos/saml-integration.png" border="false":::](https://www.youtube.com/watch?v=r2TIVBCm7v4&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=11) | [Azure AD B2C Identity Protection and Conditional Access](https://www.youtube.com/watch?v=frn5jVqbmUo&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=15) 14:44 | [:::image type="icon" source="./media/external-identities-videos/identity-protection-and-conditional-access.png" border="false":::](https://www.youtube.com/watch?v=frn5jVqbmUo&list=PL3ZTgFEc7LyuJ8YRSGXBUVItCPnQz3YX0&index=15)
3333

3434
## Azure Active Directory B2C how to series
3535

36.5 KB
Loading

articles/active-directory-b2c/technicalprofiles.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -249,6 +249,7 @@ The **InputClaim** element contains the following attributes:
249249
| --------- | -------- | ----------- |
250250
| ClaimTypeReferenceId | Yes | The identifier of a claim type. The claim is already defined in the claims schema section in the policy file or parent policy file. |
251251
| DefaultValue | No | A default value to use to create a claim if the claim indicated by ClaimTypeReferenceId doesn't exist so that the resulting claim can be used as an InputClaim element by the technical profile. |
252+
|AlwaysUseDefaultValue |No |Forces the use of the default value. |
252253
| PartnerClaimType | No | The identifier of the claim type of the external partner that the specified policy claim type maps to. If the PartnerClaimType attribute isn't specified, the specified policy claim type is mapped to the partner claim type of the same name. Use this property when your claim type name is different from the other party. An example is if the first claim name is *givenName*, while the partner uses a claim named *first_name*. |
253254

254255
## Display claims

articles/active-directory/enterprise-users/groups-write-back-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.collection: M365-identity-device-management
2020

2121
# Group writeback in the Azure Active Directory admin center (preview)
2222

23-
Group writeback is a valuable tool for administrators of Azure Active Directory (Azure AD) tenants being synced with on-premises Active Directory groups. Microsoft is now previewing new capabilities for group writeback. In this preview, you can specify in the Azure AD admin center which groups you want to write back and what you’d like each group to write back as. You can write Microsoft 365 groups back to on-premises Active Directory as Distribution, Mail-enabled Security, or Security groups, and write Security groups back as Security groups. Groups are written back with a scope of universal​.
23+
Group writeback is a valuable tool for administrators of Azure Active Directory (Azure AD) tenants being synced with on-premises Active Directory groups. Microsoft is now previewing new capabilities for group writeback for tenants with an Azure AD Premium license and Azure AD Connect version 2021 December release or later. In this preview, once you have [enabled Azure AD Connect group writeback](..//hybrid/how-to-connect-group-writeback-v2.md), you can specify in the Azure AD admin center which groups you want to write back and what you’d like each group to write back as. You can write Microsoft 365 groups back to on-premises Active Directory as Distribution, Mail-enabled Security, or Security groups, and write Security groups back as Security groups. Groups are written back with a scope of universal​.
2424

2525
>[!NOTE]
2626
> If you were previously writing Microsoft 365 groups back to on-premises Active Directory as universal distribution groups, they will appear in the Azure portal as not enabled for writeback in both the **Groups** page and in the properties page for a group. These pages display a new property introduced for the preview, “writeback enabled”. This property is not set by the current version of group writeback to ensure backward compatibility with the legacy version of group writeback and to avoid breaking existing customer setups.

articles/active-directory/hybrid/how-to-connect-group-writeback-v2.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ To enable group writeback via PowerShell:
119119
Set-ADSyncScheduler -SyncCycleEnabled $true
120120
```
121121
122-
You've now enabled the group writeback feature.
122+
You've now enabled the group writeback feature, and can [select the groups for writeback](../enterprise-users/groups-write-back-portal.md).
123123
124124
### Optional Configuration
125125
@@ -194,4 +194,5 @@ Limitations and known issues specific to Group Writeback:
194194
195195
## Next steps
196196
197-
Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).
197+
- Configure [group writeback in the Azure Active Directory Admin Center](../enterprise-users/groups-write-back-portal.md)
198+
- Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).
Lines changed: 140 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,140 @@
1+
---
2+
title: 'Tutorial: Azure AD SSO integration with Ediwin SaaS EDI'
3+
description: Learn how to configure single sign-on between Azure Active Directory and Ediwin SaaS EDI.
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: tutorial
12+
ms.date: 07/23/2022
13+
ms.author: jeedes
14+
15+
---
16+
17+
# Tutorial: Azure AD SSO integration with Ediwin SaaS EDI
18+
19+
In this tutorial, you'll learn how to integrate Ediwin SaaS EDI with Azure Active Directory (Azure AD). When you integrate Ediwin SaaS EDI with Azure AD, you can:
20+
21+
* Control in Azure AD who has access to Ediwin SaaS EDI.
22+
* Enable your users to be automatically signed-in to Ediwin SaaS EDI with their Azure AD accounts.
23+
* Manage your accounts in one central location - the Azure portal.
24+
25+
## Prerequisites
26+
27+
To get started, you need the following items:
28+
29+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
30+
* Ediwin SaaS EDI single sign-on (SSO) enabled subscription.
31+
* Along with Cloud Application Administrator, Application Administrator can also add or manage applications in Azure AD.
32+
For more information, see [Azure built-in roles](../roles/permissions-reference.md).
33+
34+
## Scenario description
35+
36+
In this tutorial, you configure and test Azure AD SSO in a test environment.
37+
38+
* Ediwin SaaS EDI supports **SP** initiated SSO.
39+
40+
## Add Ediwin SaaS EDI from the gallery
41+
42+
To configure the integration of Ediwin SaaS EDI into Azure AD, you need to add Ediwin SaaS EDI from the gallery to your list of managed SaaS apps.
43+
44+
1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
45+
1. On the left navigation pane, select the **Azure Active Directory** service.
46+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
47+
1. To add new application, select **New application**.
48+
1. In the **Add from the gallery** section, type **Ediwin SaaS EDI** in the search box.
49+
1. Select **Ediwin SaaS EDI** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
50+
51+
## Configure and test Azure AD SSO for Ediwin SaaS EDI
52+
53+
Configure and test Azure AD SSO with Ediwin SaaS EDI using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Ediwin SaaS EDI.
54+
55+
To configure and test Azure AD SSO with Ediwin SaaS EDI, perform the following steps:
56+
57+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
58+
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
59+
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
60+
1. **[Configure Ediwin SaaS EDI SSO](#configure-ediwin-saas-edi-sso)** - to configure the single sign-on settings on application side.
61+
1. **[Create Ediwin SaaS EDI test user](#create-ediwin-saas-edi-test-user)** - to have a counterpart of B.Simon in Ediwin SaaS EDI that is linked to the Azure AD representation of user.
62+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
63+
64+
## Configure Azure AD SSO
65+
66+
Follow these steps to enable Azure AD SSO in the Azure portal.
67+
68+
1. In the Azure portal, on the **Ediwin SaaS EDI** application integration page, find the **Manage** section and select **single sign-on**.
69+
1. On the **Select a single sign-on method** page, select **SAML**.
70+
1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
71+
72+
![Screenshot shows to edit Basic S A M L Configuration.](common/edit-urls.png "Basic Configuration")
73+
74+
1. On the **Basic SAML Configuration** section, perform the following steps:
75+
76+
a. In the **Identifier** textbox, type a URL using the following pattern:
77+
`https://web.sedeb2b.com/<EdiwinDomain>`
78+
79+
b. In the **Reply URL** textbox, type a URL using the following pattern:
80+
`https://web.sedeb2b.com/Ediwin/samlLogin/<EdiwinDomain>`
81+
82+
c. In the **Sign-on URL** text box, type a URL using the following pattern:
83+
`https://web.sedeb2b.com/Ediwin/samlLogin/<EdiwinDomain>`
84+
85+
> [!Note]
86+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [Ediwin SaaS EDI 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.
87+
88+
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.
89+
90+
![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
91+
92+
1. On the **Set up Ediwin SaaS EDI** section, copy the appropriate URL(s) based on your requirement.
93+
94+
![Screenshot shows to copy configuration appropriate U R L.](common/copy-configuration-urls.png "Attributes")
95+
96+
### Create an Azure AD test user
97+
98+
In this section, you'll create a test user in the Azure portal called B.Simon.
99+
100+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
101+
1. Select **New user** at the top of the screen.
102+
1. In the **User** properties, follow these steps:
103+
1. In the **Name** field, enter `B.Simon`.
104+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
105+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
106+
1. Click **Create**.
107+
108+
### Assign the Azure AD test user
109+
110+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Ediwin SaaS EDI.
111+
112+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
113+
1. In the applications list, select **Ediwin SaaS EDI**.
114+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
115+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
116+
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
117+
1. If you are expecting a role to be assigned to the users, you can select it from the **Select a role** dropdown. If no role has been set up for this app, you see "Default Access" role selected.
118+
1. In the **Add Assignment** dialog, click the **Assign** button.
119+
120+
## Configure Ediwin SaaS EDI SSO
121+
122+
To configure single sign-on on **Ediwin SaaS EDI** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Ediwin SaaS EDI support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
123+
124+
### Create Ediwin SaaS EDI test user
125+
126+
In this section, you create a user called Britta Simon in Ediwin SaaS EDI. Work with [Ediwin SaaS EDI support team](mailto:[email protected]) to add the users in the Ediwin SaaS EDI platform. Users must be created and activated before you use single sign-on.
127+
128+
## Test SSO
129+
130+
In this section, you test your Azure AD single sign-on configuration with following options.
131+
132+
* Click on **Test this application** in Azure portal. This will redirect to Ediwin SaaS EDI Sign-on URL where you can initiate the login flow.
133+
134+
* Go to Ediwin SaaS EDI Sign-on URL directly and initiate the login flow from there.
135+
136+
* You can use Microsoft My Apps. When you click the Ediwin SaaS EDI tile in the My Apps, this will redirect to Ediwin SaaS EDI 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).
137+
138+
## Next steps
139+
140+
Once you configure Ediwin SaaS EDI 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)