Skip to content

Commit 8a7da48

Browse files
authored
Merge branch 'main' into patch-1
2 parents fb98159 + f2c1e8f commit 8a7da48

File tree

3,325 files changed

+78418
-59592
lines changed

Some content is hidden

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

3,325 files changed

+78418
-59592
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -946,6 +946,7 @@
946946
"articles/machine-learning/.openpublishing.redirection.machine-learning.json",
947947
"articles/static-web-apps/.openpublishing.redirection.static-web-apps.json",
948948
".openpublishing.redirection.virtual-desktop.json",
949+
".openpublishing.redirection.deployment-environments.json",
949950
"articles/applied-ai-services/.openpublishing.redirection.applied-ai-services.json",
950951
"articles/applied-ai-services/.openpublishing.archived.json",
951952
"articles/cognitive-services/.openpublishing.redirection.cognitive-services.json",

.openpublishing.redirection.azure-monitor.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5440,6 +5440,26 @@
54405440
"source_path_from_root": "/articles/azure-monitor/insights/sql-insights-troubleshoot.md",
54415441
"redirect_url": "/azure/azure-sql/database/sql-insights-troubleshoot",
54425442
"redirect_document_id": false
5443+
},
5444+
{
5445+
"source_path_from_root": "/articles/azure-monitor/containers/container-insights-prometheus-integration.md",
5446+
"redirect_url": "/azure/azure-monitor/containers/container-insights-prometheus",
5447+
"redirect_document_id": false
5448+
},
5449+
{
5450+
"source_path_from_root": "/articles/azure-monitor/containers/container-insights-enable-existing-clusters.md",
5451+
"redirect_url": "/azure/azure-monitor/containers/container-insights-enable-aks",
5452+
"redirect_document_id": false
5453+
},
5454+
{
5455+
"source_path_from_root": "/articles/azure-monitor/containers/container-insights-enable-new-cluster.md",
5456+
"redirect_url": "/azure/azure-monitor/containers/container-insights-enable-aks",
5457+
"redirect_document_id": false
5458+
},
5459+
{
5460+
"source_path_from_root": "/articles/azure-monitor/containers/container-insights-update-metrics.md",
5461+
"redirect_url": "/azure/azure-monitor/containers/container-insights-custom-metrics",
5462+
"redirect_document_id": false
54435463
}
54445464
,
54455465
{

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -710,6 +710,16 @@
710710
"redirect_url": "/azure/defender-for-cloud/defender-for-containers-usage",
711711
"redirect_document_id": true
712712
},
713+
{
714+
"source_path_from_root": "/articles/defender-for-cloud/enable-data-collection.md",
715+
"redirect_url": "/azure/defender-for-cloud/monitoring-components",
716+
"redirect_document_id": true
717+
},
718+
{
719+
"source_path_from_root": "/articles/defender-for-cloud/defender-for-containers-usage.md",
720+
"redirect_url": "/azure/defender-for-cloud/defender-for-containers-va-acr",
721+
"redirect_document_id": true
722+
},
713723
{
714724
"source_path_from_root": "/articles/defender-for-cloud/file-integrity-monitoring-usage.md",
715725
"redirect_url": "/azure/defender-for-cloud/file-integrity-monitoring-enable-log-analytics",
@@ -720,5 +730,6 @@
720730
"redirect_url": "/azure/defender-for-cloud/release-notes#azure-monitor-agent-integration-now-in-preview",
721731
"redirect_document_id": true
722732
}
733+
723734
]
724735
}
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
{
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/deployment-environments/how-to-configure-environment-types.md",
5+
"redirect_url": "/azure/deployment-environments/how-to-configure-project-environment-types",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path_from_root": "/articles/deployment-environments/tutorial-create-and-configure-devcenter.md",
10+
"redirect_url": "/azure/deployment-environments/quickstart-create-and-configure-devcenter",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path_from_root": "/articles/deployment-environments/tutorial-create-and-configure-projects.md",
15+
"redirect_url": "/azure/deployment-environments/quickstart-create-and-configure-projects",
16+
"redirect_document_id": false
17+
}
18+
]
19+
}

.openpublishing.redirection.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,20 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/backup/sap-hana-db-manage.md",
5+
"redirect_url": "/azure/backup/sap-hana-database-manage",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/backup/sap-hana-db-restore.md",
10+
"redirect_url": "/azure/backup/sap-hana-database-restore",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/backup/sap-hana-db-about.md",
15+
"redirect_url": "/azure/backup/sap-hana-database-about",
16+
"redirect_document_id": false
17+
},
318
{
419
"source_path_from_root": "/articles/storage/blobs/storage-quickstart-blobs-dotnet-legacy.md",
520
"redirect_url": "/azure/storage/blobs/storage-quickstart-blobs-dotnet",
@@ -11313,6 +11328,11 @@
1131311328
"redirect_url": "/azure/ddos-protection/telemetry",
1131411329
"redirect_document_id": false
1131511330
},
11331+
{
11332+
"source_path_from_root": "/articles/ddos-protection/ddos-protection-standard-features.md",
11333+
"redirect_url": "/azure/ddos-protection/ddos-protection-features",
11334+
"redirect_document_id": false
11335+
},
1131611336
{
1131711337
"source_path_from_root": "/articles/asc-for-iot/index.yml",
1131811338
"redirect_url": "/azure/defender-for-iot/",

articles/active-directory-b2c/json-transformations.md

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 08/10/2022
12+
ms.date: 09/07/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -251,6 +251,26 @@ The following claims transformation outputs a JSON string claim that will be the
251251
}
252252
```
253253

254+
The **GenerateJson** claims transformation accepts plain strings. If an input claim contains a JSON string, that string will be escaped. In the following example, if you use email output from [CreateJsonArray above](json-transformations.md#example-of-createjsonarray), that is ["[email protected]"], as an input parameter, the email will look like as shown in the following JSON claim:
255+
256+
- Output claim:
257+
- **requestBody**:
258+
259+
```json
260+
{
261+
"customerEntity":{
262+
"email":"[\"[email protected]\"]",
263+
"userObjectId":"01234567-89ab-cdef-0123-456789abcdef",
264+
"firstName":"John",
265+
"lastName":"Smith",
266+
"role":{
267+
"name":"Administrator",
268+
"id": 1
269+
}
270+
}
271+
}
272+
```
273+
254274
## GetClaimFromJson
255275

256276
Get a specified element from a JSON data. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-transformation/json#getclaimfromjson) of this claims transformation.

articles/active-directory-b2c/user-profile-attributes.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,10 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 09/24/2021
11+
ms.date: 10/11/2021
1212
ms.author: kengaderdus
1313
ms.subservice: B2C
14+
ms.custom: b2c-support
1415
---
1516

1617
# User profile attributes
@@ -48,7 +49,7 @@ The table below lists the [user resource type](/graph/api/resources/user) attrib
4849
|creationType |String|If the user account was created as a local account for an Azure Active Directory B2C tenant, the value is LocalAccount or nameCoexistence. Read only.|No|No|Persisted, Output|
4950
|dateOfBirth |Date|Date of birth.|No|No|Persisted, Output|
5051
|department |String|The name for the department in which the user works. Max length 64.|Yes|No|Persisted, Output|
51-
|displayName |String|The display name for the user. Max length 256.|Yes|Yes|Persisted, Output|
52+
|displayName |String|The display name for the user. Max length 256. \< \> characters aren't allowed. | Yes|Yes|Persisted, Output|
5253
|facsimileTelephoneNumber<sup>1</sup>|String|The telephone number of the user's business fax machine.|Yes|No|Persisted, Output|
5354
|givenName |String|The given name (first name) of the user. Max length 64.|Yes|Yes|Persisted, Output|
5455
|jobTitle |String|The user's job title. Max length 128.|Yes|Yes|Persisted, Output|
@@ -165,7 +166,7 @@ In user migration scenarios, if the accounts you want to migrate have weaker pas
165166

166167
## MFA phone number attribute
167168

168-
When using a phone for multi-factor authentication (MFA), the mobile phone is used to verify the user identity. To [add](/graph/api/authentication-post-phonemethods) a new phone number programmatically, [update](/graph/api/b2cauthenticationmethodspolicy-update), [get](/graph/api/b2cauthenticationmethodspolicy-get), or [delete](/graph/api/phoneauthenticationmethod-delete) the phone number, use MS Graph API [phone authentication method](/graph/api/resources/phoneauthenticationmethod).
169+
When using a phone for multi-factor authentication (MFA), the mobile phone is used to verify the user identity. To [add](/graph/api/authentication-post-phonemethods) a new phone number programmatically, [update](/graph/api/phoneauthenticationmethod-update), [get](/graph/api/phoneauthenticationmethod-get), or [delete](/graph/api/phoneauthenticationmethod-delete) the phone number, use MS Graph API [phone authentication method](/graph/api/resources/phoneauthenticationmethod).
169170

170171
In Azure AD B2C [custom policies](custom-policy-overview.md), the phone number is available through `strongAuthenticationPhoneNumber` claim type.
171172

articles/active-directory/app-proxy/what-is-application-proxy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.workload: identity
1111
ms.date: 08/29/2022
1212
ms.author: kenwith
1313
ms.reviewer: ashishj
14-
ms.custom: has-adal-ref
14+
ms.custom: has-adal-ref, ignite-2022
1515
---
1616

1717
# Using Azure AD Application Proxy to publish on-premises apps for remote users
@@ -134,7 +134,7 @@ The following diagram illustrates in general how Azure AD authentication service
134134

135135
|**Component**|**Description**|
136136
|:-|:-|
137-
|Endpoint|The endpoint is a URL or an [user portal](../manage-apps/end-user-experiences.md). Users can reach applications while outside of your network by accessing an external URL. Users within your network can access the application through a URL or an user portal. When users go to one of these endpoints, they authenticate in Azure AD and then are routed through the connector to the on-premises application.|
137+
|Endpoint|The endpoint is a URL or an [user portal](../manage-apps/end-user-experiences.md). Users can reach applications while outside of your network by accessing an external URL. Users within your network can access the application through a URL or a user portal. When users go to one of these endpoints, they authenticate in Azure AD and then are routed through the connector to the on-premises application.|
138138
|Azure AD|Azure AD performs the authentication using the tenant directory stored in the cloud.|
139139
|Application Proxy service|This Application Proxy service runs in the cloud as part of Azure AD. It passes the sign-on token from the user to the Application Proxy Connector. Application Proxy forwards any accessible headers on the request and sets the headers as per its protocol, to the client IP address. If the incoming request to the proxy already has that header, the client IP address is added to the end of the comma-separated list that is the value of the header.|
140140
|Application Proxy connector|The connector is a lightweight agent that runs on a Windows Server inside your network. The connector manages communication between the Application Proxy service in the cloud and the on-premises application. The connector only uses outbound connections, so you don't have to open any inbound ports or put anything in the DMZ. The connectors are stateless and pull information from the cloud as necessary. For more information about connectors, like how they load-balance and authenticate, see [Understand Azure AD Application Proxy connectors](./application-proxy-connectors.md).|

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ description: Learn how to move your organization away from less secure authentic
55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
8+
ms.custom: ignite-2022
89
ms.topic: conceptual
910
ms.date: 06/23/2022
1011

@@ -13,8 +14,7 @@ author: mjsantani
1314
manager: amycolannino
1415

1516
ms.collection: M365-identity-device-management
16-
17-
# Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Authenticator app in Azure AD to improve and secure user sign-in events.
17+
#Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Authenticator app in Azure AD to improve and secure user sign-in events.
1818
---
1919
# How to run a registration campaign to set up Microsoft Authenticator - Microsoft Authenticator
2020

@@ -277,7 +277,7 @@ The feature aims to empower admins to get users set up with MFA using the Authen
277277

278278
If this user doesn’t have the Authenticator app set up for push notifications and is enabled for it by policy, yes, the user will see the nudge.
279279

280-
**Will a user who has a the Authenticator app setup only for TOTP codes see the nudge?** 
280+
**Will a user who has the Authenticator app setup only for TOTP codes see the nudge?** 
281281

282282
Yes. If the Authenticator app is not set up for push notifications and the user is enabled for it by policy, yes, the user will see the nudge.
283283

@@ -308,4 +308,4 @@ It's the same as snoozing.
308308

309309
## Next steps
310310

311-
[Enable passwordless sign-in with Microsoft Authenticator](howto-authentication-passwordless-phone.md)
311+
[Enable passwordless sign-in with Microsoft Authenticator](howto-authentication-passwordless-phone.md)

articles/active-directory/azuread-dev/videos.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: conceptual
1010
ms.workload: identity
1111
ms.date: 02/12/2020
1212
ms.author: marsma
13-
ms.custom: aaddev
13+
ms.custom: aaddev, ignite-2022
1414
ms.reviewer: celested
1515
ROBOTS: NOINDEX
1616
---
@@ -21,7 +21,7 @@ Learn about the new Microsoft identity platform and how to migrate to it from th
2121

2222
## Migrate from v1.0 to v2.0
2323

24-
**Learn about migrating to the the latest version of the Microsoft identity platform**
24+
**Learn about migrating to the latest version of the Microsoft identity platform**
2525

2626
:::row:::
2727
:::column:::

0 commit comments

Comments
 (0)