Skip to content

Commit 65e4d2e

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram23-0103
2 parents c32689f + 1919f11 commit 65e4d2e

File tree

6 files changed

+29
-19
lines changed

6 files changed

+29
-19
lines changed
80.2 KB
Loading
-77.6 KB
Loading
56.5 KB
Loading

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

Lines changed: 26 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: tutorial
12-
ms.date: 11/21/2022
12+
ms.date: 01/05/2023
1313
ms.author: jeedes
1414
---
1515

@@ -72,11 +72,11 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
7272

7373
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Base64)**. Select **Download** to download the certificate and save it on your computer.
7474

75-
![Screenshot of SAML Signing Certificate section, with Download link highlighted](common/certificatebase64.png)
75+
![Screenshot of SAML Signing Certificate section, with Download link highlighted.](common/certificatebase64.png)
7676

7777
1. Veracode 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 the list of default attributes.
7878

79-
![Screenshot of User Attributes & Claims section](common/default-attributes.png)
79+
![Screenshot of User Attributes & Claims section.](common/default-attributes.png)
8080

8181
1. Veracode also expects a few more attributes to be passed back in the SAML response. These attributes are also pre-populated, but you can review them per your requirements.
8282

@@ -88,7 +88,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8888

8989
1. On the **Set up Veracode** section, copy the appropriate URL(s) based on your requirement.
9090

91-
![Screenshot of Set up Veracode section, with configuration URLs highlighted](common/copy-configuration-urls.png)
91+
![Screenshot of Set up Veracode section, with configuration URLs highlighted.](common/copy-configuration-urls.png)
9292

9393
### Create an Azure AD test user
9494

@@ -116,43 +116,52 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
116116

117117
## Configure Veracode SSO
118118

119-
1. In a different web browser window, sign in to your Veracode company site as an administrator.
119+
Notes:
120+
121+
* These instructions assume you are using the new [Single Sign On/Just-in-Time Provisioning feature from Veracode](https://docs.veracode.com/r/Signing_On). To activate this feature if it is not already active, please contact Veracode Support.
122+
* These instructions are valid for all [Veracode regions](https://docs.veracode.com/r/Region_Domains_for_Veracode_APIs).
123+
124+
1. In a different web browser window, sign in to your Veracode company site as an administrator.
120125

121126
1. From the menu on the top, select **Settings** > **Admin**.
122127

123-
![Screenshot of Veracode Administration, with Settings icon and Admin highlighted](./media/veracode-tutorial/admin.png "Administration")
128+
![Screenshot of Veracode Administration, with Settings icon and Admin highlighted.](./media/veracode-tutorial/admin.png "Administration")
124129

125130
1. Select the **SAML** tab.
126131

127-
1. In the **Organization SAML Settings** section, perform the following steps:
132+
1. In the **SAML Certificate** section, perform the following steps:
128133

129-
![Screenshot of Organization SAML Settings section](./media/veracode-tutorial/saml.png "Administration")
134+
![Screenshot of Organization SAML Settings section.](./media/veracode-tutorial/saml.png "Administration")
130135

131136
a. For **Issuer**, paste the value of the **Azure AD Identifier** that you've copied from the Azure portal.
132137

133138
b. For **Assertion Signing Certificate**, select **Choose File** to upload your downloaded certificate from the Azure portal.
134139

135-
c. For **Self Registration**, select **Enable Self Registration**.
140+
c. Note the values of the three URLs (**SAML Assertion URL**, **SAML Audience URL**, **Relay state URL**).
141+
142+
d. Click **Save**.
143+
144+
1. Take the values of the **SAML Assertion URL**, **SAML Audience URL** and **Relay state URL** and update them in the Azure Active Directory settings for the Veracode integration.
145+
146+
1. Select the **JIT Provisioning** tab.
147+
148+
![Screenshot of JIT Provisioning tab, with various options highlighted.](./media/veracode-tutorial/just-in-time.png "JIT Provisioning")
136149

137-
1. In the **Self Registration Settings** section, perform the following steps, and then select **Save**:
150+
1. In the **Organization Settings** section, toggle the **Configure Default Settings for Just-in-Time user provisioning** setting to **On**.
138151

139-
![Screenshot of Self Registration Settings section, with various options highlighted](./media/veracode-tutorial/save.png "Administration")
152+
1. In the **Basic Settings** section, for **User Data Updates**, select **Prefer Veracode User Data**.
140153

141-
a. For **New User Activation**, select **No Activation Required**.
154+
1. In the **Access Settings** section, under **User Roles**, select from the following For more information about Veracode user roles, see the [Veracode Documentation](https://docs.veracode.com/r/c_role_permissions):
142155

143-
b. For **User Data Updates**, select **Preference Veracode User Data**.
156+
![Screenshot of JIT Provisioning User Roles, with various options highlighted.](./media/veracode-tutorial/user-roles.png "JIT Provisioning")
144157

145-
c. For **SAML Attribute Details**, select the following:
146-
* **User Roles**
147158
* **Policy Administrator**
148159
* **Reviewer**
149160
* **Security Lead**
150161
* **Executive**
151162
* **Submitter**
152163
* **Creator**
153164
* **All Scan Types**
154-
* **Team Memberships**
155-
* **Default Team**
156165

157166
### Create Veracode test user
158167

articles/cosmos-db/restore-account-continuous-backup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@ Restore-AzCosmosDBAccount `
194194
```
195195
### To restore a continuous account that is configured with managed identity using CLI
196196

197-
To restore Customer Managed Key (CMK) continuous account please refer to the steps provided [here](./how-to-setup-customer-managed-keys.md#to-restore-a-continuous-account-that-is-configured-with-managed-identity-using-cli)
197+
To restore Customer Managed Key (CMK) continuous account please refer to the steps provided [here](./how-to-setup-customer-managed-keys.md)
198198

199199
### <a id="get-the-restore-details-powershell"></a>Get the restore details from the restored account
200200

articles/reliability/migrate-app-service.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to migrate Azure App Service to availability zone support
55
author: anaharris-ms
66
ms.service: app-service
77
ms.topic: conceptual
8-
ms.date: 12/12/2022
8+
ms.date: 12/14/2022
99
ms.author: anaharris
1010
ms.reviewer: jordanselig
1111
ms.custom: references_regions
@@ -46,6 +46,7 @@ Availability zone support is a property of the App Service plan. The following a
4646
- Japan East
4747
- North Europe
4848
- Qatar Central
49+
- South Africa North
4950
- South Central US
5051
- Southeast Asia
5152
- Sweden Central

0 commit comments

Comments
 (0)