Skip to content

Commit 80a706d

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patch-303
2 parents b16ca28 + 9dbcf24 commit 80a706d

File tree

89 files changed

+7127
-522
lines changed

Some content is hidden

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

89 files changed

+7127
-522
lines changed

articles/active-directory-b2c/add-api-connector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ Content-type: application/json
146146
"displayName": "John Smith",
147147
"objectId": "11111111-0000-0000-0000-000000000000",
148148
"givenName":"John",
149-
"lastName":"Smith",
149+
"surname":"Smith",
150150
"step": "PostFederationSignup",
151151
"client_id":"<guid>",
152152
"ui_locales":"en-US"

articles/active-directory-b2c/app-registrations-training-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ In the legacy experience, apps were always created as customer-facing applicatio
5959
> [!NOTE]
6060
> This option is required to be able to run Azure AD B2C user flows to authenticate users for this application. Learn [how to register an application for use with user flows.](tutorial-register-applications.md)
6161
62-
You can also use this option to use Azure AD B2C as a SAML service provider. [Learn more](identity-provider-adfs.md).
62+
You can also use this option to use Azure AD B2C as a SAML service provider. [Learn more](saml-service-provider.md).
6363

6464
## Applications for DevOps scenarios
6565

articles/active-directory/fundamentals/whats-new-archive.md

Lines changed: 144 additions & 355 deletions
Large diffs are not rendered by default.

articles/application-gateway/application-gateway-faq.yml

Lines changed: 34 additions & 31 deletions
Large diffs are not rendered by default.

articles/application-gateway/application-gateway-probe-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ By default, an HTTP(S) response with status code between 200 and 399 is consider
7676
The following are matching criteria:
7777

7878
- **HTTP response status code match** - Probe matching criterion for accepting user specified http response code or response code ranges. Individual comma-separated response status codes or a range of status code is supported.
79-
- **HTTP response body match** - Probe matching criterion that looks at HTTP response body and matches with a user specified string. The match only looks for presence of user specified string in response body and isn't a full regular expression match.
79+
- **HTTP response body match** - Probe matching criterion that looks at HTTP response body and matches with a user specified string. The match only looks for presence of user specified string in response body and isn't a full regular expression match. The specified match must be 4090 characters or less.
8080

8181
Match criteria can be specified using the `New-AzApplicationGatewayProbeHealthResponseMatch` cmdlet.
8282

articles/azure-monitor/logs/api/access-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: article
1010

1111
You can submit a query request to a workspace using the Azure Monitor Log Analytics endpoint `https://api.loganalytics.azure.com`. To access the endpoint, you must authenticate through Azure Active Directory (Azure AD).
1212
>[!Note]
13-
> The `api.loganalytics.io` endpoint is being replaced by `api.loganalytics.azure.com`. `api.loganalytics.io` will continue to be be supported for the forseeable future.
13+
> The `api.loganalytics.io` endpoint is being replaced by `api.loganalytics.azure.com`. `api.loganalytics.io` will continue to be supported for the forseeable future.
1414
## Authenticating with a demo API key
1515

1616
To quickly explore the API without Azure Active Directory authentication, use the demonstration workspace with sample data, which supports API key authentication.

articles/azure-monitor/roles-permissions-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article shows how to quickly apply a built-in monitoring role to a user in
1818

1919
## Built-in monitoring roles
2020

21-
Built-in roles in Azure Monitor help limit access to resources in a subscription while still enabling staff who monitor infrastructure to obtain and configure the data they need. Azure Monitor provides two out-of-the-box roles: Monitoring Reader and Monitoring Contributor.
21+
Built-in roles in Azure Monitor help limit access to resources in a subscription while still enabling staff who monitor infrastructure to obtain and configure the data they need. Azure Monitor provides two out-of-the-box roles: Monitoring Reader and Monitoring Contributor. Azure Monitor Logs also provides built-in roles for managing access to data in a Log Analytics workspace, as described in [Manage access to Log Analytics workspaces](./logs/manage-access.md).
2222

2323
### Monitoring Reader
2424

articles/container-apps/microservices-dapr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ az role assignment create --assignee $PRINCIPAL_ID \
209209
```azurepowershell
210210
Install-Module Az.Resources
211211
212-
New-AzRoleAssignment -ObjectId $PrincipalId -RoleDefinitionName 'Storage Blob Data Contributor' -Scope '/subscriptions/$SubscriptionId/resourceGroups/$ResourceGroupName/providers/Microsoft.Storage/storageAccounts/$StorageAcctName'
212+
New-AzRoleAssignment -ObjectId $PrincipalId -RoleDefinitionName 'Storage Blob Data Contributor' -Scope "/subscriptions/$SubscriptionId/resourceGroups/$ResourceGroupName/providers/Microsoft.Storage/storageAccounts/$StorageAcctName"
213213
```
214214

215215
---

articles/data-factory/connector-office-365.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,6 @@ This Microsoft 365 (Office 365) connector is supported for the following capabil
2828
|---------| --------|
2929
|[Copy activity](copy-activity-overview.md) (source/-)|&#9312;|
3030
|[Mapping data flow](concepts-data-flow-overview.md) (source/-)|&#9312;|
31-
|[Lookup activity](control-flow-lookup-activity.md) (source/-)|&#9312;|
3231

3332
<small>*&#9312; Azure integration runtime &#9313; Self-hosted integration runtime*</small>
3433

@@ -362,9 +361,5 @@ To create a mapping data flow using the Microsoft 365 connector as a source, com
362361

363362
6. On the tab **Data preview** click on the **Refresh** button to fetch a sample dataset for validation.
364363

365-
## Lookup activity properties
366-
367-
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
368-
369364
## Next steps
370365
For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/data-factory/includes/data-factory-v2-supported-data-stores-for-lookup-activity.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,6 @@ ms.custom: include file, ignite-2022
8181
| &nbsp; |[Azure Data Explorer (Kusto)](../connector-azure-data-explorer.md) |
8282
| &nbsp; |[Magento (Preview)](../connector-magento.md) |
8383
| &nbsp; |[Marketo (Preview)](../connector-marketo.md) |
84-
| &nbsp; |[Microsoft 365](../connector-office-365.md) |
8584
| &nbsp; |[Oracle Eloqua (Preview)](../connector-oracle-eloqua.md) |
8685
| &nbsp; |[Oracle Responsys (Preview)](../connector-oracle-responsys.md) |
8786
| &nbsp; |[Oracle Service Cloud (Preview)](../connector-oracle-service-cloud.md) |

0 commit comments

Comments
 (0)