Merge pull request #290865 from MicrosoftDocs/main

11/21 11:00 AM IST Publish

Author: PhilKang0704

articles/azure-resource-manager/bicep/operator-null-forgiving.md

@@ -20,7 +20,7 @@ The following example fails the design time validation:
 ```bicep
 param inputString string
 
-output outString string = first(skip(split(input, '/'), 1))
+output outString string = first(skip(split(inputString, '/'), 1))
 ```
 
 The warning message is:
@@ -34,7 +34,7 @@ To solve the problem, use the null-forgiving operator:
 ```bicep
 param inputString string
 
-output outString string = first(skip(split(input, '/'), 1))!
+output outString string = first(skip(split(inputString, '/'), 1))!
 ```
 
 ## Next steps

articles/batch/batch-virtual-network.md

@@ -2,7 +2,7 @@
 title: Provision a pool in a virtual network
 description: Learn how to create a Batch pool in an Azure virtual network so that compute nodes can communicate securely with other VMs in the network, such as a file server.
 ms.topic: how-to
-ms.date: 06/27/2024
+ms.date: 11/19/2024
 ---
 
 # Create an Azure Batch pool in a virtual network
@@ -70,11 +70,13 @@ Batch creates a network security group (NSG) at the network interface level of e
 In order to provide the necessary communication between compute nodes and the Batch service, these NSGs are configured such that:
 
 * Inbound TCP traffic on ports 29876 and 29877 from Batch service IP addresses that correspond to the BatchNodeManagement.*region* service tag. This rule is only created in `classic` pool communication mode.
-* Inbound TCP traffic on port 22 (Linux nodes) or port 3389 (Windows nodes) to permit remote access for SSH or RDP on default ports, respectively. For certain types of multi-instance tasks on Linux, such as MPI, you may need to allow SSH traffic for IPs in the subnet containing Batch compute nodes. Certain MPI runtimes may require launching over SSH, which is typically routed on private IP address space. This traffic might be blocked per subnet-level NSG rules.
 * Outbound any traffic on port 443 to Batch service IP addresses that correspond to the BatchNodeManagement.*region* service tag.
 * Outbound traffic on any port to the virtual network. This rule might be amended per subnet-level NSG rules.
 * Outbound traffic on any port to the Internet. This rule might be amended per subnet-level NSG rules.
 
+> [!NOTE]
+> For pools created using an API version earlier than `2024-07-01`, inbound TCP traffic on port 22 (Linux nodes) or port 3389 (Windows nodes) is configured to allow remote access via SSH or RDP on the default ports.
+
 > [!IMPORTANT]
 > Use caution if you modify or add inbound or outbound rules in Batch-configured NSGs. If communication to the compute nodes in the specified subnet is denied by an NSG, the Batch service will set the state of the compute nodes to **unusable**. Additionally, no resource locks should be applied to any resource created by Batch, because this can prevent cleanup of resources as a result of user-initiated actions such as deleting a pool.
 

articles/batch/security-best-practices.md

@@ -1,7 +1,7 @@
 ---
 title: Batch security and compliance best practices
 description: Learn best practices and useful tips for enhancing security with your Azure Batch solutions.
-ms.date: 08/08/2024
+ms.date: 11/21/2024
 ms.topic: conceptual
 ---
 
@@ -69,7 +69,7 @@ Batch management operations via Azure Resource Manager are encrypted using HTTPS
 
 ### Batch pool compute nodes
 
-The Batch service communicates with a Batch node agent that runs on each node in the pool. For example, the service instructs the node agent to run a task, stop a task, or get the files for a task. Communication with the node agent is enabled by one or more load balancers, the number of which depends on the number of nodes in a pool. The load balancer forwards the communication to the desired node, with each node being addressed by a unique port number. By default, load balancers have public IP addresses associated with them. You can also remotely access pool nodes via RDP or SSH (this access is enabled by default, with communication via load balancers).
+The Batch service communicates with a Batch node agent that runs on each node in the pool. For example, the service instructs the node agent to run a task, stop a task, or get the files for a task. Communication with the node agent is enabled by one or more load balancers, the number of which depends on the number of nodes in a pool. The load balancer forwards the communication to the desired node, with each node being addressed by a unique port number. By default, load balancers have public IP addresses associated with them. You can also remotely access pool nodes via RDP or SSH, see [Configure remote access to compute nodes in an Azure Batch pool](pool-endpoint-configuration.md).
 
 #### Batch compute node OS
 
@@ -158,9 +158,11 @@ For more information, see [Create a pool without public IP addresses](simplified
 
 #### Limit remote access to pool nodes
 
-By default, Batch allows a node user with network connectivity to connect externally to a compute node in a Batch pool by using RDP or SSH.
+For pools created with an API version earlier than `2024-07-01`, Batch by default permits a node user with network connectivity to externally connect to a compute node in a Batch pool using RDP or SSH.
 
-To limit remote access to nodes, use one of the following methods:
+To limit remote access, create your pools using an API version `2024-07-01` or later.
+
+To limit remote access to nodes in pools created by API with version earlier than `2024-07-01`, use one of the following methods:
 
 - Configure the [PoolEndpointConfiguration](/rest/api/batchservice/pool/add#poolendpointconfiguration) to deny access. The appropriate network security group (NSG) will be associated with the pool.
 - Create your pool [without public IP addresses](simplified-node-communication-pool-no-public-ip.md). By default, these pools can't be accessed outside of the VNet.

articles/communication-services/concepts/analytics/logs/call-automation-logs.md

@@ -76,7 +76,6 @@ Communication Services offers the following types of logs that you can enable:
 | `ServerCallId` | A unique ID to identify a call. |
 | `SDKVersion` | The SDK version used for the request. |
 | `SDKType` | The SDK type used for the request. |
-| `ParticipantId` | The ID to identify the call participant that made the request. |
 | `SubOperationName` | The name that's used to identify the subtype of media operation (play or recognize). |
 |`operationID`| The ID that's used to correlate asynchronous events.|
 

articles/communication-services/concepts/call-automation/call-automation.md

@@ -39,7 +39,7 @@ The following features are currently available in the Azure Communication Servic
 |                       | Place new outbound call to one or more endpoints  | ✔️    | ✔️    |     ✔️         |    ✔️   |
 |                       | Redirect* (forward) a call to one or more endpoints  | ✔️    | ✔️    |     ✔️         |    ✔️   |
 |                       | Reject an incoming call                           | ✔️    | ✔️    |     ✔️         |    ✔️   |
-|                       | Connect to an ongoing call or Room (in preview)   | ✔️    | ✔️    |     ✔️         |    ✔️   |
+|                       | Connect to an ongoing call or Room                | ✔️    | ✔️    |     ✔️         |    ✔️   |
 | Mid-call scenarios    | Add one or more endpoints to an existing call     | ✔️    | ✔️    |     ✔️         |    ✔️   |
 |                       | Cancel adding an endpoint to an existing call     | ✔️    | ✔️    |     ✔️         |    ✔️   |
 |                       | Play Audio from an audio file                     | ✔️    | ✔️    |     ✔️         |    ✔️   |
@@ -64,7 +64,7 @@ The following features are currently available in the Azure Communication Servic
 |                       | List all participants in a call                   | ✔️    | ✔️    |     ✔️         |    ✔️   |
 | Call Recording        | Start/pause/resume/stop recording                 | ✔️    | ✔️    |     ✔️         |    ✔️   |
 
-\* Transfer or redirect of a VoIP call to a phone number is currently not supported.
+\* Redirect of a VoIP call to a phone number is not supported.
 
 ## Architecture
 
@@ -84,11 +84,11 @@ These actions are performed before the destination endpoint listed in the `Incom
 
 **Reject** – To reject a call means your application can receive the `IncomingCall` event and prevent the call from being connected to the destination endpoint.
 
-**Redirect** – Using the `IncomingCall` event from Event Grid, you can redirect a call to one or more endpoints creating a single or simultaneous ringing (sim-ring) scenario. Redirect action doesn't answer the call. The call is redirected or forwarded to another destination endpoint to be answered.
+**Redirect** – Using the `IncomingCall` event from Event Grid, you can redirect a call to another endpoint. Redirect action doesn't answer the call. The call is redirected or forwarded to another destination endpoint to be answered.
 
 **Create Call** - Use the Create Call action to place outbound calls to phone numbers and to other communication users. Use cases include your application placing outbound calls to proactively inform users about an outage or notify about an order update.
 
-**Connect Call** (in preview) - Use the Connect Call action to connect to an ongoing call and take call actions on it. You can also use this action to connect and [manage a Rooms call programmatically](./../../quickstarts/rooms/manage-rooms-call.md), like performing PSTN dial outs for Room using your service. 
+**Connect Call** - Use the Connect Call action to connect to an ongoing call and take call actions on it. You can also use this action to connect and [manage a Rooms call programmatically](./../../quickstarts/rooms/manage-rooms-call.md), like performing PSTN dial outs for Room using your service. 
 
 ### Mid-call actions
 
@@ -153,6 +153,7 @@ The Call Automation events are sent to the web hook callback URI specified when
 | `CallConnected` | The call successfully started (when using `Answer` or `Create` action) or your application successfully connected to an ongoing call (when using `Connect` action). |
 | `CallDisconnected` | Your application has been disconnected from the call. |
 | `CreateCallFailed` | Your application has failed to create the call. |
+| `AnswerFailed` | Your application has failed to answer the call. |
 | `ConnectFailed` | Your application failed to connect to a call (for `Connect` call action only). |
 | `CallTransferAccepted` | Transfer action successfully completed and the transferee is connected to the target participant. |
 | `CallTransferFailed` | The transfer action failed. |

articles/communication-services/how-tos/call-automation/actions-for-call-control.md

@@ -166,9 +166,9 @@ The response provides you with CallConnection object that you can use to take fu
 2. `ParticipantsUpdated` event that contains the latest list of participants in the call.
 ![Sequence diagram for placing an outbound call.](media/make-call-flow.png)
 
-In the case where the call fails, you will receive a `CallDisconnected` and `CreateCallFailed` event with error codes for further troubleshooting (see [this page](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md) for more information on Call Automation error codes).
+In the case where the call fails, you will receive a `CallDisconnected` and `CreateCallFailed` event with error codes for further troubleshooting (see [this page](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md) for more information on error codes).
 
-## Connect to a call (in preview)
+## Connect to a call
 
 Connect action enables your service to establish a connection with an ongoing call and take actions on it. This is useful to manage a Rooms call or when client applications started a 1:1 or group call that Call automation isn't part of. Connection is established using the CallLocator property and can be of types: ServerCallLocator, GroupCallLocator, and RoomCallLocator. These IDs can be found when the call is originally established or a Room is created, and also published as part of [CallStarted](./../../../event-grid/communication-services-voice-video-events.md#microsoftcommunicationcallstarted) event. 
 
@@ -303,6 +303,8 @@ The response provides you with CallConnection object that you can use to take fu
 
 ![Sequence diagram for answering an incoming call.](media/answer-flow.png)
 
+In the case where answer operation fails, you will receive a `AnswerFailed` event with error codes for further troubleshooting (see [this page](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md) for more information on error codes).
+
 ## Reject a call
 
 You can choose to reject an incoming call as shown below. You can provide a reject reason: none, busy or forbidden. If nothing is provided, none is chosen by default.

articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md

@@ -16,8 +16,6 @@ services: azure-communication-services
 
 # Add a Microsoft Teams user to an existing call using Call Automation
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 In this quickstart, we use the Azure Communication Services Call Automation APIs to add, remove, and transfer call to a Teams user.
 
 ## Prerequisites

articles/communication-services/samples/email-detect-sensitive-content.md

@@ -71,6 +71,8 @@ From the application directory, install the Azure Communication Services Email c
 
 `dotnet add package Microsoft.Azure.CognitiveServices.ContentModerator`
 
+`dotnet add package Azure.AI.ContentSafety`
+
 ## Create the Main function
 
 Open `Program.cs` and replace the existing contents with the following code. The `using` directives include the `Azure.Communication.Email` and `Azure.AI namespaces`. The rest of the code outlines the `SendMail` function for your program.
@@ -189,7 +191,7 @@ static async Task<bool> AnalyzeInappropriateContent(List<string> documents)
 
 ### Create the Content Safety client with authentication
 
-Create a new function with a Content Safety client that also retrieves your connection information. Add the following code into the `AnalyzeInappropriateContent` function to retrieve the connection key and endpoint for the resource from environment variables named `CONTENT_LANGUAGE_KEY` and `CONTENT_LANGUAGE_ENDPOINT`. It also creates a new `ContentSafetyClient` variable. If you're using the same Azure AI instance for Text Analytics, these values remain the same. For more information about managing your Content Safety connection information, see [Quickstart: Detect Personally Identifiable Information (PII) > Create environment variables](/azure/ai-services/language-service/personally-identifiable-information/quickstart#create-environment-variables). 
+Create a new function with a Content Safety client that also retrieves your connection information. Add the following code into the `AnalyzeInappropriateContent` function to retrieve the connection key and endpoint for the resource from environment variables named `CONTENT_LANGUAGE_KEY` and `CONTENT_LANGUAGE_ENDPOINT`. It also creates a new `ContentSafetyClient` variable. If you're using the same Azure AI instance for Text Analytics, these values remain the same. For more information about managing your Content Safety connection information, see [Quickstart: Create the Content Safety resource](/azure/ai-services/content-safety/how-to/use-blocklist?tabs=windows%2Ccsharp#prerequisites).
 
 ```csharp
 // This example requires environment variables named "CONTENT_LANGUAGE_KEY" and "CONTENT_LANGUAGE_ENDPOINT"

articles/data-factory/connector-deprecation-plan.md

@@ -7,7 +7,7 @@ ms.service: azure-data-factory
 ms.subservice: data-movement
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 11/06/2024
+ms.date: 11/18/2024
 ---
 
 # Upgrade plan for Azure Data Factory connectors
@@ -33,13 +33,13 @@ This article describes future upgrades for some connectors of Azure Data Factory
 | [Concur (Preview)](connector-concur.md) |/ | End of support announced | December 31, 2024 | December 31, 2024 | 
 | [Couchbase (Preview)](connector-couchbase.md) |/ | End of support announced | December 31, 2024 | December 31, 2024 | 
 | [Drill](connector-drill.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
-| [Hbase](connector-hbase.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
+| [HBase](connector-hbase.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
 | [Magento (Preview)](connector-magento.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
 | [Marketo (Preview)](connector-marketo.md) |/ | End of support announced  | December 31, 2024| December 31, 2024 | 
 | [Oracle Eloqua (Preview)](connector-oracle-eloqua.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
 | [Oracle Responsys (Preview)](connector-oracle-responsys.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
 | [Oracle Service Cloud (Preview)](connector-oracle-service-cloud.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
-| [Paypal (Preview)](connector-paypal.md) |/ | End of support announced  |December 31, 2024 | December 31, 2024| 
+| [PayPal (Preview)](connector-paypal.md) |/ | End of support announced  |December 31, 2024 | December 31, 2024| 
 | [Phoenix](connector-phoenix.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
 | [Salesforce Marketing Cloud](connector-salesforce-marketing-cloud.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
 | [Zoho (Preview)](connector-zoho.md) |/ | End of support announced  | December 31, 2024 | December 31, 2024 | 
@@ -77,13 +77,13 @@ The following connectors are scheduled for deprecation on December 31, 2024. You
 - [Concur (Preview)](connector-concur.md)
 - [Couchbase (Preview)](connector-couchbase.md)
 - [Drill](connector-drill.md)
-- [Hbase](connector-hbase.md)
+- [HBase](connector-hbase.md)
 - [Magento (Preview)](connector-magento.md)
 - [Marketo (Preview)](connector-marketo.md)
 - [Oracle Eloqua (Preview)](connector-oracle-eloqua.md)
 - [Oracle Responsys (Preview)](connector-oracle-responsys.md)
 - [Oracle Service Cloud (Preview)](connector-oracle-service-cloud.md)
-- [Paypal (Preview)](connector-paypal.md)
+- [PayPal (Preview)](connector-paypal.md)
 - [Phoenix](connector-phoenix.md)
 - [Salesforce Marketing Cloud](connector-salesforce-marketing-cloud.md)
 - [Zoho (Preview)](connector-zoho.md)

articles/data-factory/parameterize-linked-services.md

@@ -5,7 +5,7 @@ description: Learn how to parameterize linked services in Azure Data Factory and
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 08/06/2024
+ms.date: 11/18/2024
 author: kromerm
 ms.author: makromer
 ---
@@ -83,6 +83,7 @@ All the linked service types are supported for parameterization.
 - SharePoint Online List
 - Snowflake
 - SQL Server
+- Vertica
 
 **Advanced authoring:** For other linked service types that are not in above list, you can parameterize the linked service by editing the JSON on UI: