Merge pull request #311784 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-13 06:00 UTC

Author: learn-build-service-prod[bot]

articles/dev-box/concept-authoring-troubleshooting-guide-team-customizations.md

@@ -5,17 +5,19 @@ description: "Enhance your Microsoft Dev Box workflows with this guide to author
 author: mikeparker104
 ms.author: miparker
 ms.reviewer: rosemalcolm
-ms.date: 12/11/2025
+ms.date: 02/06/2026
 ms.topic: concept-article
 ms.service: dev-box
+ms.custom:
+  - ai-usage: ai-assisted
 ---
 
 # Authoring and troubleshooting guide for team customizations
 
 This guide provides recommendations for creating Microsoft Dev Box image definition files (`imagedefinition.yaml`). It pulls together and extends content from existing documentation to raise visibility of effective approaches, common pitfalls, and troubleshooting guidance. The intent is to aid in onboarding and building reliable, maintainable customizations that work consistently for your development teams.
 
 > [!NOTE]
-> This guide builds on the [Create a dev box by using team customizations quickstart](/azure/dev-box/quickstart-team-customizations). If you're new to Dev Box customizations, complete that tutorial first.
+> This guide builds on [Configure team customizations](/azure/dev-box/how-to-configure-team-customizations). If you're new to Dev Box customizations, review that article first.
 
 This guide covers strategies for:
 
@@ -33,11 +35,11 @@ Before you begin, ensure you have:
 | Development environment | Dev Box with local admin permissions. Visual Studio (VS) Code with latest version. Dev Box extension installed and GitHub Copilot extension installed. |
 
 > [!TIP]
-> For comprehensive background on Dev Box customizations, see [Team Customizations documentation](/azure/dev-box/concept-what-are-team-customizations?tabs=team-customizations) and [How to write an image definition file](/azure/dev-box/how-to-write-image-definition-file).
+> For comprehensive background on Dev Box customizations, see [Dev Box customizations overview](/azure/dev-box/concept-what-are-dev-box-customizations) and [Configure team customizations](/azure/dev-box/how-to-configure-team-customizations).
 
 ## Approach recommendations
 
-When authoring Dev Box customizations, choose the approach that best fits your team's workflow and technical requirements. For background on how customizations work, see [Use Team Customizations](/azure/dev-box/quickstart-team-customizations).
+When authoring Dev Box customizations, choose the approach that best fits your team's workflow and technical requirements. For background on how customizations work, see [Configure team customizations](/azure/dev-box/how-to-configure-team-customizations).
 
 ### Start with the authoring agent
 
@@ -183,7 +185,7 @@ parameters:
 - **Document security assumptions** for future maintainers
 
 > [!TIP]
-> For comprehensive guidance on using secrets, see [Use Azure Key Vault secrets in customization files](/azure/dev-box/how-to-use-secrets-customization-files).
+> For comprehensive guidance on using secrets, see [Connect to Azure resources or clone private repositories](/azure/dev-box/how-to-customizations-connect-resource-repository).
 
 ### Ensure WinGet package discovery
 
@@ -313,13 +315,8 @@ tasks:
 
 ## Related content
 
-- [Create a dev box by using team customizations (prerequisite quickstart)](/azure/dev-box/quickstart-team-customizations)
-- [Team Customizations documentation](/azure/dev-box/concept-what-are-team-customizations?tabs=team-customizations)
-- [Write an image definition file for Dev Box Team Customizations](/azure/dev-box/how-to-write-image-definition-file)
 - [Configure team customizations](/azure/dev-box/how-to-configure-team-customizations)
-- [System tasks and user tasks](/azure/dev-box/how-to-configure-team-customizations#system-tasks-and-user-tasks)
-- [Use Azure Key Vault secrets in customization files](/azure/dev-box/how-to-use-secrets-customization-files)
-- [Create an image definition file with Copilot](/azure/dev-box/how-to-use-copilot-generate-image-definition-file)
+- [Dev Box customizations overview](/azure/dev-box/concept-what-are-dev-box-customizations)
+- [Connect to Azure resources or clone private repositories](/azure/dev-box/how-to-customizations-connect-resource-repository)
 - [Example YAML customization file](https://aka.ms/devcenter/preview/imaging/examples)
-- [Add and configure a catalog](/azure/dev-box/how-to-configure-catalog)
-- [Dev Box image definition instructions (GitHub Copilot)](https://github.com/github/awesome-copilot/blob/main/instructions/devbox-image-definition.instructions.md)
+- [Add and configure a catalog](/azure/dev-box/how-to-configure-catalog)

articles/event-hubs/event-hubs-faq.yml

@@ -3,7 +3,7 @@ metadata:
   title: Frequently asked questions - Azure Event Hubs | Microsoft Docs
   description: This article provides a list of frequently asked questions (FAQ) for Azure Event Hubs and their answers. 
   ms.topic: faq
-  ms.date: 09/30/2024
+  ms.date: 02/09/2026
   ms.custom: sfi-ropc-nochange
 title: Event Hubs frequently asked questions
 summary: |
@@ -84,7 +84,7 @@ sections:
       - question: |
           What configuration changes need to be done for my existing application to talk to Event Hubs?
         answer: |
-          To connect to an event hub, you'll need to update the Kafka client configs. It's done by creating an Event Hubs namespace and obtaining the [connection string](event-hubs-get-connection-string.md). Change the bootstrap.servers to point the Event Hubs FQDN and the port to 9093. Update the sasl.jaas.config to direct the Kafka client to your Event Hubs endpoint (which is the connection string you've obtained), with correct authentication as shown below:
+          To connect to an event hub, you need to update the Kafka client configs. It's done by creating an Event Hubs namespace and obtaining the [connection string](event-hubs-get-connection-string.md). Change the bootstrap.servers to point the Event Hubs FQDN and the port to 9093. Update the sasl.jaas.config to direct the Kafka client to your Event Hubs endpoint (which is the connection string you've obtained), with correct authentication as shown here:
           
           ```properties
           bootstrap.servers={YOUR.EVENTHUBS.FQDN}:9093
@@ -105,7 +105,7 @@ sections:
           ```
           
           > [!NOTE]
-          > If sasl.jaas.config isn't a supported configuration in your framework, find the configurations that are used to set the SASL username and password and use them instead. Set the username to $ConnectionString and the password to your Event Hubs connection string.
+          > If sasl.jaas.config isn't a supported configuration in your framework, find the configurations that are used to set the Simple Authentication and Security Layer (SASL) username and password and use them instead. Set the username to $ConnectionString and the password to your Event Hubs connection string.
           
       - question: |
           What is the message/event size for Event Hubs?
@@ -195,7 +195,7 @@ sections:
           [!INCLUDE [event-hubs-partition-count](./includes/event-hubs-partition-count.md)]
           
       - question: |  
-          Can partition count be increased in the Standard tier of Event Hubs?
+          Can I increase the partition count in the Standard tier of Event Hubs?
         answer: |
           No, it's not possible because partitions are immutable in the Standard tier. Dynamic addition of partitions is available only in premium and dedicated tiers of Event Hubs.
           
@@ -219,7 +219,7 @@ sections:
       - question: |
           How are ingress events calculated?
         answer: |
-          Each event sent to an event hub counts as a billable message. An *ingress event* is defined as a unit of data that is less than or equal to 64 KB. Any event that is less than or equal to 64 KB in size is considered to be one billable event. If the event is greater than 64 KB, the number of billable events is calculated according to the event size, in multiples of 64 KB. For example, an 8-KB event sent to the event hub is billed as one event, but a 96-KB message sent to the event hub is billed as two events.
+          Each event sent to an event hub counts as a billable message. An *ingress event* is defined as a unit of data that's less than or equal to 64 KB. Any event that's less than or equal to 64 KB in size is considered to be one billable event. If the event is greater than 64 KB, the number of billable events is calculated according to the event size, in multiples of 64 KB. For example, an 8-KB event sent to the event hub is billed as one event, but a 96-KB message sent to the event hub is billed as two events.
           
           Events consumed from an event hub, and management operations and control calls such as checkpoints, aren't counted as billable ingress events, but accrue up to the throughput unit allowance.
           

articles/event-hubs/schema-registry-overview.md

@@ -2,7 +2,7 @@
 title: Azure Schema Registry in Azure Event Hubs
 description: This article provides an overview of Schema Registry support by Azure Event Hubs and how it can be used from your Apache Kafka and other apps.
 ms.topic: concept-article
-ms.date: 12/02/2024
+ms.date: 02/09/2026
 ms.custom: references_regions
 # Customer intent: As an Azure Event Hubs user, I want to know how Azure Event Hubs supports registering schemas and using them in sending and receiving events. 
 ---
@@ -11,24 +11,24 @@ ms.custom: references_regions
 
 Event streaming and messaging scenarios often deal with structured data in the event or message payload. However, the structured data is of little value to the event broker, which only deals with bytes. Schema-driven formats such as [Apache Avro](https://avro.apache.org/), [JSONSchema](https://json-schema.org/), or [Protobuf](https://protobuf.dev/) are often used to serialize or deserialize such structured data to/from binary.
 
-An event producer uses a schema definition to serialize event payload and publish it to an event broker such as Event Hubs. Event consumers read event payload from the broker and deserialize it using the same schema definition. 
+An event producer uses a schema definition to serialize the event payload and publish it to an event broker such as Event Hubs. Event consumers read the event payload from the broker and deserialize it by using the same schema definition. 
 
-So, both producers and consumers can validate the integrity of the data with the same schema. 
+Both producers and consumers can validate the integrity of the data by using the same schema. 
 
-:::image type="content" source="./media/schema-registry-overview/schema-driven-ser-de.svg" alt-text="Image showing producers and consumers serializing and deserializing event payload using schemas from the Schema Registry. ":::
+:::image type="content" source="./media/schema-registry-overview/schema-driven-ser-de.svg" alt-text="Diagram showing producers and consumers serializing and deserializing event payload using schemas from the Schema Registry. " lightbox="./media/schema-registry-overview/schema-driven-ser-de.svg":::
 
 ## What is Azure Schema Registry?
-**Azure Schema Registry** is a feature of Event Hubs, which provides a central repository for schemas for event-driven and messaging-centric applications. It provides the flexibility for your producer and consumer applications to **exchange data without having to manage and share the schema**. It also provides a simple governance framework for reusable schemas and defines relationship between schemas through a logical grouping construct (schema groups).
+**Azure Schema Registry** is a feature of Event Hubs that provides a central repository for schemas for event-driven and messaging-centric applications. It provides the flexibility for your producer and consumer applications to **exchange data without having to manage and share the schema**. It also provides a simple governance framework for reusable schemas and defines relationship between schemas through a logical grouping construct (schema groups).
 
-:::image type="content" source="./media/schema-registry-overview/schema-registry.svg" alt-text="Image showing a producer and a consumer serializing and deserializing event payload using a schema from the Schema Registry." border="false":::
+:::image type="content" source="./media/schema-registry-overview/schema-registry.svg" alt-text="Diagram showing a producer and a consumer serializing and deserializing event payload using a schema from the Schema Registry." lightbox="./media/schema-registry-overview/schema-registry.svg" border="false":::
 
-With schema-driven serialization frameworks like Apache Avro, JSONSchema and Protobuf, moving serialization metadata into shared schemas can also help with **reducing the per-message overhead**. It's because each message doesn't need to have the metadata (type information and field names) as it's the case with tagged formats such as JSON. 
+With schema-driven serialization frameworks like Apache Avro, JSONSchema, and Protobuf, moving serialization metadata into shared schemas can also help **reduce the per-message overhead**. Each message doesn't need to include the metadata (type information and field names) as it does with tagged formats such as JSON. 
 
 > [!NOTE]
-> The feature is available in the **Standard**, **Premium**, and **Dedicated** tier.
+> The feature is available in the **Standard**, **Premium**, and **Dedicated** tiers.
 >
 
-Having schemas stored alongside the events and inside the eventing infrastructure ensures that the metadata required for serialization or deserialization is always in reach and schemas can't be misplaced. 
+Storing schemas alongside the events and inside the eventing infrastructure ensures that the metadata required for serialization or deserialization is always available and schemas can't be misplaced. 
 
 ## Related content