Skip to content

Commit 126a5a2

Browse files
authored
Merge pull request #292025 from MicrosoftDocs/main
12/16/2024 PM Publish
2 parents b4e214f + 75854a2 commit 126a5a2

File tree

81 files changed

+186
-157
lines changed

Some content is hidden

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

81 files changed

+186
-157
lines changed

articles/app-service/app-service-undelete.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: article
88
ms.custom: devx-track-azurepowershell
99
---
1010

11-
# Restore deleted App Service app Using PowerShell
11+
# Restore Deleted App Service App Using PowerShell
1212

1313
If you happened to accidentally delete your app in Azure App Service, you can restore it using the commands from the [Az PowerShell module](/powershell/azure/).
1414

articles/app-service/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -403,11 +403,11 @@
403403
href: deploy-intelligent-apps.md
404404
- name: WordPress
405405
items:
406+
- name: WordPress overview
407+
href: overview-wordpress.md
406408
- name: WordPress architecture
407409
displayName: WordPress on App Service architecture
408410
href: /azure/architecture/example-scenario/infrastructure/wordpress-app-service
409-
- name: WordPress overview
410-
href: overview-wordpress.md
411411
- name: Deploy WordPress
412412
displayName: Create a WordPress site
413413
href: quickstart-wordpress.md

articles/azure-vmware/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,6 @@ items:
5353
href: enable-sql-azure-hybrid-benefit.md
5454
- name: Save costs with a reserved instance
5555
href: reserved-instance.md
56-
- name: Azure hybrid benefit for Windows Server, SQL Server, and Linux subscriptions
57-
href: sql-server-hybrid-benefit.md
5856
- name: VMware Cloud Foundations (VCF) license portability on Azure VMware Solution
5957
href: vmware-cloud-foundations-license-portability.md
6058
- name: Architecture

articles/batch/pool-endpoint-configuration.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configure node endpoints in Azure Batch pool
33
description: How to configure node endpoints such as access to SSH or RDP ports on compute nodes in an Azure Batch pool.
44
ms.topic: how-to
5-
ms.date: 11/08/2024
5+
ms.date: 12/16/2024
66
---
77

88
# Configure remote access to compute nodes in an Azure Batch pool
@@ -12,10 +12,11 @@ externally to a compute node in a Batch pool. For example, a user can connect by
1212
compute node in a Windows pool. Similarly, by default, a user can connect by Secure Shell (SSH) on port 22 to a compute
1313
node in a Linux pool.
1414

15-
> [!TIP]
16-
> As of API version `2024-07-01`, Batch no longer automatically maps common remote access ports for SSH and RDP.
17-
> If you wish to allow remote access to your Batch compute nodes with pools created with API version `2024-07-01` or later,
18-
> then you must manually configure the pool endpoint configuration to enable such access.
15+
> [!NOTE]
16+
> As of API version `2024-07-01` (and all pools created after **30 November 2025** regardless of API version), Batch no
17+
> longer automatically maps common remote access ports for SSH and RDP. If you wish to allow remote access to your Batch
18+
> compute nodes with pools created with API version `2024-07-01` or later (and after 30 November 2025), then you must
19+
> manually configure the pool endpoint configuration to enable such access.
1920
2021
In your environment, you might need to enable, restrict, or disable external access settings or any other ports you wish
2122
on the Batch pool. You can modify these settings by using the Batch APIs to set the
@@ -167,4 +168,4 @@ class AzureBatch(object):
167168
## Next steps
168169

169170
- Learn about the [Batch service workflow and primary resources](batch-service-workflow-features.md) such as pools, nodes, jobs, and tasks.
170-
- For more information about NSG rules in Azure, see [Filter network traffic with network security groups](../virtual-network/network-security-groups-overview.md).
171+
- Learn more about NSG rules in Azure with [Filtering network traffic with network security groups](../virtual-network/network-security-groups-overview.md).

articles/data-factory/concepts-datasets-linked-services.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ ms.reviewer: jburchel
88
ms.subservice: data-movement
99
ms.topic: conceptual
1010
ms.custom: synapse
11-
ms.date: 01/05/2024
11+
ms.date: 12/16/2024
12+
ai-usage: ai-assisted
1213
---
1314

1415
# Datasets in Azure Data Factory and Azure Synapse Analytics
@@ -144,6 +145,9 @@ For example, for a Delimited Text dataset, the dataset type is set to **Delimite
144145
}
145146
```
146147

148+
> [!NOTE]
149+
> The schema value is defined using JSON syntax. For more detailed information on schema mapping and data type mapping, refer to the [Azure Data Factory Copy Activity Schema and Type Mapping](copy-activity-schema-and-type-mapping.md) documentation.
150+
147151
## Create datasets
148152
You can create datasets by using one of these tools or SDKs: [.NET API](quickstart-create-data-factory-dot-net.md), [PowerShell](quickstart-create-data-factory-powershell.md), [REST API](quickstart-create-data-factory-rest-api.md), Azure Resource Manager Template, and Azure portal
149153

@@ -156,9 +160,16 @@ Here are some differences between datasets in Data Factory current version (and
156160
- Scoped datasets (datasets defined in a pipeline) aren’t supported in the current version.
157161

158162
## Related content
163+
164+
### Quickstarts
165+
159166
See the following tutorial for step-by-step instructions for creating pipelines and datasets by using one of these tools or SDKs.
160167

161168
- [Quickstart: create a data factory using .NET](quickstart-create-data-factory-dot-net.md)
162169
- [Quickstart: create a data factory using PowerShell](quickstart-create-data-factory-powershell.md)
163170
- [Quickstart: create a data factory using REST API](quickstart-create-data-factory-rest-api.md)
164171
- [Quickstart: create a data factory using Azure portal](quickstart-create-data-factory-portal.md)
172+
173+
### Dataset schema references
174+
- [Azure Data Factory Copy Activity Schema and Type Mapping](copy-activity-schema-and-type-mapping.md)
175+
- [Azure Data Factory Concepts - Datasets and Linked Services](concepts-datasets-linked-services.md)

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

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,8 @@ ms.topic: conceptual
77
ms.author: jianleishen
88
author: jianleishen
99
ms.custom: synapse
10-
ms.date: 08/02/2024
10+
ms.date: 12/16/2024
11+
ai-usage: ai-assisted
1112
---
1213
# Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM using Azure Data Factory or Azure Synapse Analytics
1314

@@ -500,6 +501,15 @@ To write data into a lookup field with multiple targets like Customer and Owner,
500501

501502
1. Map both the value and entity-reference columns from source to sink. The entity-reference column must be mapped to a virtual column with the special naming pattern `{lookup_field_name}@EntityReference`. The column doesn't actually exist in Dynamics. It's used to indicate this column is the metadata column of the given multitarget lookup field.
502503

504+
### Setting the Owner field
505+
506+
When setting the Owner field in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM, it is important to provide a valid reference. The valid options for the `@EntityReference` are:
507+
508+
- `systemuser`: This refers to an individual user within the system.
509+
- `team`: This refers to a team of users within the organization.
510+
511+
Ensure that the value provided corresponds to one of these options to avoid errors during data transformation.
512+
503513
For example, assume the source has these two columns:
504514

505515
- **CustomerField** column of type **GUID**, which is the primary key value of the target entity in Dynamics.

articles/event-grid/concepts-event-grid-namespaces.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
11
---
2-
ms.date: 11/15/2023
2+
ms.date: 12/16/2024
33
author: robece
44
ms.author: robece
55
title: Concepts for Event Grid namespace topics
66
description: General concepts of Event Grid namespace topics and their main functionality such as pull and push delivery.
7-
ms.topic: conceptual
8-
ms.custom:
9-
- ignite-2023
10-
- build-2024
7+
ms.topic: concept-article
8+
# Customer intent: I want to know concepts of Azure Event Grid namespaces.
119
---
1210

1311
# Azure Event Grid namespace concepts
@@ -131,7 +129,7 @@ Event Grid uses Event Hubs SDK to send events to Event Hubs using [AMQP](https:/
131129

132130
[!INCLUDE [differences-between-consumption-modes](./includes/differences-between-consumption-modes.md)]
133131

134-
## Next steps
132+
## Related content
135133

136134
* For an introduction to Event Grid, see [About Event Grid](overview.md).
137135
* To get started using namespace topics, refer to [publish events using namespace topics](publish-events-using-namespace-topics.md).

articles/event-grid/consume-private-endpoints.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,8 @@
22
title: Deliver events using private link service
33
description: This article describes how to work around push delivery's limitation to deliver events using private link service.
44
ms.topic: how-to
5-
ms.custom:
6-
- ignite-2023
7-
ms.date: 11/15/2023
5+
ms.date: 12/16/2024
6+
# Customer intent: I would like to know if delivering events using private link service is supported in the Push model.
87
---
98

109
# Deliver events using private link service
@@ -50,5 +49,5 @@ If there's no firewall or virtual network rules configured for the destination S
5049

5150
If a firewall or virtual network rule is configured for the destination Storage account, Event Hubs namespace, or Service Bus namespace, you can use only the system-assigned managed identity if **Allow Azure services on the trusted service list to access the storage account** is also enabled on the destinations. You can't use user-assigned managed identity whether this option is enabled or not.
5251

53-
## Next steps
52+
## Related content
5453
For more information about delivering events using a managed identity, see [Event delivery using a managed identity](managed-service-identity.md).

articles/event-grid/event-domains.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
22
title: Event Domains in Azure Event Grid
33
description: This article describes how to use event domains to manage the flow of custom events to your various business organizations, customers, or applications.
4-
ms.topic: conceptual
5-
ms.custom:
6-
- ignite-2023
7-
ms.date: 11/15/2023
4+
ms.topic: concept-article
5+
ms.date: 12/16/2024
6+
# Customer intent: I want to know what event domains in Azure Event Grid are and how to use them.
87
---
98

109
# Understand event domains for managing Event Grid topics
@@ -119,6 +118,6 @@ Event domains handle publishing to topics for you. Instead of publishing events
119118

120119
Event domains use the same [operations pricing](https://azure.microsoft.com/pricing/details/event-grid/) that all other features in Event Grid use. Operations work the same in event domains as they do in custom topics. Each ingress of an event to an event domain is an operation, and each delivery attempt for an event is an operation.
121120

122-
## Next steps
121+
## Related content
123122

124123
To learn about setting up event domains, creating topics, creating event subscriptions, and publishing events, see [Manage event domains](./how-to-event-domains.md).

articles/event-grid/event-schema-communication-services.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
---
2-
title: Azure Communication Services as an Event Grid source - Overview
3-
description: This article describes how to use Azure Communication Services as an Event Grid event source.
4-
ms.topic: conceptual
5-
ms.date: 09/19/2023
2+
title: Azure Communication Services as an Event Grid source
3+
description: This article describes how to use Azure Communication Services as an Event Grid event source and what events are supported.
4+
ms.topic: concept-article
5+
ms.date: 12/16/2024
66
ms.author: mikben
7+
# Customer intent: I want to know what events Azure Communication Services support via Azure Event Grid.
78
---
89

910
# Azure Communication Services as an Azure Event Grid source
1011

11-
Azure Communication Services integrates with [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to deliver real-time event notifications in a reliable, scalable, and secure manner. The purpose of this article is to help you configure your applications to listen to Communication Services events. For example, you may want to update a database, create a work item and deliver a push notification whenever an SMS message is received by a phone number associated with your Communication Services resource.
12+
Azure Communication Services integrates with [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to deliver real-time event notifications in a reliable, scalable, and secure manner. The purpose of this article is to help you configure your applications to listen to Communication Services events. For example, you might want to update a database, create a work item and deliver a push notification whenever an SMS message is received by a phone number associated with your Communication Services resource.
1213

1314
Azure Event Grid is a fully managed event routing service, which uses a publish-subscribe model. Event Grid has built-in support for Azure services like [Azure Functions](../azure-functions/functions-overview.md) and [Azure Logic Apps](../azure-functions/functions-overview.md). It can deliver event alerts to non-Azure services using webhooks. For a complete list of the event handlers that Event Grid supports, see [An introduction to Azure Event Grid](overview.md).
1415

@@ -19,7 +20,7 @@ Azure Event Grid is a fully managed event routing service, which uses a publish-
1920
2021
## Events types
2122

22-
Event grid uses [event subscriptions](concepts.md#event-subscriptions) to route event messages to subscribers.
23+
Event Grid uses [event subscriptions](concepts.md#event-subscriptions) to route event messages to subscribers.
2324

2425
Azure Communication Services emits the following event types:
2526

@@ -55,7 +56,7 @@ The following example shows a filter for all SMS messages and delivery reports s
5556
}
5657
```
5758

58-
## Next steps
59+
## Related content
5960

6061
* For an introduction to Azure Event Grid, see [What is Event Grid?](./overview.md)
6162
* For an introduction to Azure Event Grid Concepts, see [Concepts in Event Grid?](./concepts.md)

0 commit comments

Comments
 (0)