Custom .Net deserializer for Azure Stream Analytics will be retired on 30 September 2024.

Custom .net deserializer for Azure Stream Analytics will be retired on 30 September 2024\. After that date, it won't be possible to use the feature. Please transition to a JSON, AVRO, or CSV built-in deserializer by that date. The custom .net deserializer (public preview) lets customers read data from other file formats, such as XML and other user-defined formats. While it became a valuable tool for many, overall adoption didn't grow as much as we hoped. We continuously adjust to changing market conditions and adapt our investments to where they can have the greatest impact. As a result of this ongoing effort, we've made the difficult decision to retire the custom .net deserializer for Azure Stream Analytics. No new features or updates will be added, but we'll continue to provide technical support and recommendations for the custom .net deserializer until it retires on 30 September 2024. ## **Required action** Please transition to a built-in deserializer before 30 September 2024\. We recommend exploring these tools and services: | File format | Recommended alternative | | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | JSON | We recommend using the built-in [JSON deserializer](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-parsing-json) for Azure Stream Analytics. | | AVRO | For AVRO, Azure Stream Analytics supports a built-in [AVRO deserializer.](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-parsing-json) | | CSV | For CSV, Azure Stream Analytics supports a [built-in CSV deserializer](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-parsing-json). | | Protobuf | We recommend pre-processing your events to convert the file format into JSON before ingesting into any of the supported inputs Azure Stream Analytics supports, such as Event Hub, IoT Hub, or Blob Input. | | XML | We recommend pre-processing your events to convert the file format into JSON before ingesting into any of the supported inputs Azure Stream Analytics supports, such as Event Hub, IoT Hub, or Blob Input. | | Bond and other custom file formats | We recommend pre-processing your events to convert the file format into JSON before ingesting into any of the supported inputs Azure Stream Analytics supports, such as Event Hub, IoT Hub, or Blob Input. | Example scenario We recommend using any industry-leading tool to convert your file format to JSON, CSV, or AVRO. For example, you can use [Azure Functions](https://learn.microsoft.com/azure/azure-functions/functions-scenarios?pivots=programming-language-csharp#real-time-stream-and-event-processing) to pre-process XML events and convert them to JSON before ingesting them into an EventHub and connecting to your Azure Stream Analytics job. ## **More information** The custom .net deserializer allowed Azure Stream Analytics to read from any custom file format. With the retirement of the custom .net deserializer, the only file formats Azure Stream Analytics can read from are those with built-in support, such as JSON, CSV, or AVRO. ## **Help and support** Our support team will be available to address any queries or concerns you may have. Please email us at [askasa@microsoft.com](mailto:askasa@microsoft.com). _Learn more about service retirements that may impact your resources in the [Azure Retirement Workbook](https://aka.ms/ServicesRetirementWorkbook). Please note that retirements may not be visible in the workbook for up to two weeks after being announced._ * Azure Stream Analytics * Retirements * [ Azure Stream Analytics](https://azure.microsoft.com/en-gb/products/stream-analytics/)