Merge pull request #304391 from KendalBond007/IOTDepIncludeUpdate_18Aug25

JillGrant615 · web-flow · commit 675f6ae427ca · 2025-08-21T12:53:17.000-06:00
Iot dep include update 18 aug25
diff --git a/articles/healthcare-apis/includes/iot-deprecation.md b/articles/healthcare-apis/includes/iot-deprecation.md
@@ -0,0 +1,14 @@
+---
+title: Retirement banner
+author: KendalBond007
+ms.service: azure-health-data-services
+ms.topic: include
+ms.date: 08/19/2025
+ms.author: chachachachami
+---
+
+> [!IMPORTANT]
+> The deprecation of the MedTech service was initiated 3 May 2025.
+> If using a MedTech service is no longer a priority, deprovision your instance, which can be found [here](https://ms.portal.azure.com/#browse/Microsoft.HealthcareApis%2Fworkspaces%2Fiotconnectors).
+> Support for active instances in the following regions will end 3 May 2028: West US2, UK South, West Europe, East US, Australia East, East US 2, Central India, North Europe. 
+> The Open Source version of the MedTech service can be found [here](https://learn.microsoft.com/azure/healthcare-apis/iot/git-projects#medtech-service-github-projects).
diff --git a/articles/healthcare-apis/iot/concepts-machine-learning.md b/articles/healthcare-apis/iot/concepts-machine-learning.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # MedTech service and Azure Machine Learning Service
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 In this article, learn about using the MedTech service and the Azure Machine Learning Service.
 
diff --git a/articles/healthcare-apis/iot/concepts-power-bi.md b/articles/healthcare-apis/iot/concepts-power-bi.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # MedTech service and Microsoft Power BI
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 In this article, learn about using the MedTech service and Microsoft Power Business Intelligence (Power BI).
 
diff --git a/articles/healthcare-apis/iot/concepts-teams.md b/articles/healthcare-apis/iot/concepts-teams.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # MedTech service and Microsoft Teams notifications
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 In this article, learn about using the MedTech service and Microsoft Teams for notifications.
 
diff --git a/articles/healthcare-apis/iot/configure-metrics.md b/articles/healthcare-apis/iot/configure-metrics.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Monitor performance metrics for the MedTech service
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 Gain insights into the health, availability, latency, traffic, and errors of your organization's MedTech services by monitoring MedTech service metrics in the Azure portal. To help you identify patterns or trends, pin tiles for the metrics to an Azure portal dashboard for easy access and visualization.
 
diff --git a/articles/healthcare-apis/iot/deploy-arm-template.md b/articles/healthcare-apis/iot/deploy-arm-template.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using an Azure Resource Manager template
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 To implement infrastructure as code for your Azure solutions, use Azure Resource Manager templates (ARM templates). The template is a [JavaScript Object Notation (JSON)](https://www.json.org/) file that defines the infrastructure and configuration for your project. The template uses declarative syntax, which lets you state what you intend to deploy without having to write the sequence of programming commands to create it. In the template, you specify the resources to deploy and the properties for those resources. 
 
diff --git a/articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md b/articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md
@@ -16,8 +16,7 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using a Bicep file and Azure PowerShell or the Azure CLI
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 Bicep is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. In a Bicep file, you define the infrastructure you want to deploy to Azure, and then use that file throughout the development lifecycle to repeatedly deploy your infrastructure. Your resources are deployed in a consistent manner Bicep provides concise syntax, reliable type safety, and support for code reuse. Bicep offers a first-class authoring experience for your infrastructure-as-code solutions in Azure.
 
diff --git a/articles/healthcare-apis/iot/deploy-choose-method.md b/articles/healthcare-apis/iot/deploy-choose-method.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Quickstart: Choose a deployment method for the MedTech service
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages that allow you to customize your deployment to suit your needs and use cases.
 
diff --git a/articles/healthcare-apis/iot/deploy-json-powershell-cli.md b/articles/healthcare-apis/iot/deploy-json-powershell-cli.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 To implement infrastructure as code for your Azure solutions, use Azure Resource Manager templates (ARM templates). The template is a JavaScript Object Notation (JSON) file that defines the infrastructure and configuration for your project. The template uses declarative syntax, which lets you state what you intend to deploy without having to write the sequence of programming commands to create it. In the template, you specify the resources to deploy and the properties for those resources. 
 
diff --git a/articles/healthcare-apis/iot/deploy-manual-portal.md b/articles/healthcare-apis/iot/deploy-manual-portal.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using the Azure portal
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 The MedTech service deployment using the Azure portal is divided into the following three sections:
 
diff --git a/articles/healthcare-apis/iot/device-messages-through-iot-hub.md b/articles/healthcare-apis/iot/device-messages-through-iot-hub.md
@@ -13,8 +13,7 @@ ms.author: chrupa
 
 # Tutorial: Receive device messages through Azure IoT Hub
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 The MedTech service can receive messages from devices you create and manage through an IoT hub in [Azure IoT Hub](../../iot-hub/iot-concepts-and-iot-hub.md). This tutorial uses an Azure Resource Manager template (ARM template) and a **Deploy to Azure** button to deploy a MedTech service. The template also deploys an IoT hub to create and manage devices, and message routes device messages to an event hub for the MedTech service to read and process. After device data processing, the FHIR&reg; resources are persisted in the FHIR service, which is also included in the template.
 
diff --git a/articles/healthcare-apis/iot/frequently-asked-questions.md b/articles/healthcare-apis/iot/frequently-asked-questions.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 ---
 # MedTech service FAQ
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 ## Where is the MedTech service available?
 
diff --git a/articles/healthcare-apis/iot/get-started.md b/articles/healthcare-apis/iot/get-started.md
@@ -12,8 +12,7 @@ ms.custom: mode-api
 
 # Get started with the MedTech service 
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article and diagram outlines the basic steps to get started with the MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md). These steps might help you to assess the [MedTech service deployment methods](deploy-choose-method.md) and determine which deployment method is best for you.
 
diff --git a/articles/healthcare-apis/iot/git-projects.md b/articles/healthcare-apis/iot/git-projects.md
@@ -12,19 +12,18 @@ ms.author: chrupa
 
 # Open-source projects
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 Check out our open-source software (OSS) projects on GitHub, which provide source code and instructions to deploy services for various use cases with the MedTech service.
 
 > [!IMPORTANT]
-> Links to OSS projects on the GitHub website are for informational purposes only and do not constitute an endorsement or guarantee of any kind.  You should review the information and licensing terms on the OSS projects on GitHub before using it.  
+> The links to OSS projects on the GitHub website are for informational purposes only and do not constitute an endorsement or guarantee of any kind.  You should review the information and licensing terms on the OSS projects on GitHub before using it.  
 
 ## MedTech service GitHub projects
 
 ### FHIR integration
 
-* [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): Open-source version of the Azure Health Data Services MedTech service managed service. Can be used with any FHIR&reg; service that supports [HL7 FHIR](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491).
+* [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): Open-source version of the Azure Health Data Services MedTech service managed service. Can be used with any Fast Healthcare Interoperability Resources (FHIR&reg;) service that supports [HL7 FHIR](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491).
 
 ### Wearables integration
 
diff --git a/articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md b/articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # How to enable diagnostic settings for the MedTech service
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 In this article, learn how to enable diagnostic settings for the MedTech service to:
 
diff --git a/articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md b/articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md
@@ -10,8 +10,7 @@ ms.author: chrupa
 ---
 # How to use CalculatedContent templates with the MedTech service device mapping
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides an overview of how to use CalculatedContent templates within a MedTech service device mapping.
 
diff --git a/articles/healthcare-apis/iot/how-to-use-custom-functions.md b/articles/healthcare-apis/iot/how-to-use-custom-functions.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # How to use custom functions with the MedTech service device mapping
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 Many functions are available when using **JMESPath** as the expression language. Besides the built-in functions available as part of the [JMESPath specification](https://jmespath.org/specification.html#built-in-functions), many more custom functions can also be used. This article describes how to use the MedTech service-specific custom functions with the MedTech service [device mapping](overview-of-device-mapping.md).
 
diff --git a/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md b/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # How to use IotJsonPathContent templates with the MedTech service device mapping
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides an overview of how to use IotJsonPathContent templates within a MedTech service device mapping.
 
diff --git a/articles/healthcare-apis/iot/how-to-use-mapping-debugger.md b/articles/healthcare-apis/iot/how-to-use-mapping-debugger.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # How to use the MedTech service Mapping debugger (Preview)
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 > [!IMPORTANT]
 > This capability is currently available for Public Preview and is subject to change. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
diff --git a/articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md b/articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # How to use the MedTech service monitoring and health checks tabs
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 In this article, learn how to use the MedTech service monitoring and health check tabs in the Azure portal. The monitoring and health check tabs provide access to crucial MedTech service metrics and health checks. These metrics and health checks can be used in assessing the health and performance of your MedTech service and can be useful seeing patterns and/or trends or assisting with troubleshooting your MedTech service.
 
diff --git a/articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md b/articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Overview of the MedTech service device data processing stages 
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides an overview of the device data processing stages within the [MedTech service](overview.md). The MedTech service transforms device data into [FHIR&reg; Observations](https://www.hl7.org/fhir/observation.html) for persistence in the [FHIR service](../fhir/overview.md).
 
diff --git a/articles/healthcare-apis/iot/overview-of-device-mapping.md b/articles/healthcare-apis/iot/overview-of-device-mapping.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # Overview of the MedTech service device mapping
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides an overview of the MedTech service device mapping.
 
diff --git a/articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md b/articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md
@@ -11,8 +11,7 @@ ms.author: chrupa
 
 # Overview of the MedTech service FHIR destination mapping
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides an overview of the MedTech service FHIR&reg; destination mapping.
 
diff --git a/articles/healthcare-apis/iot/overview-of-samples.md b/articles/healthcare-apis/iot/overview-of-samples.md
@@ -12,9 +12,7 @@ ms.author: chrupa
 
 # Overview of the MedTech service scenario-based mappings samples
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
-
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 The [MedTech service](overview.md) scenario-based [samples](https://github.com/Azure-Samples/azure-health-data-and-ai-samples/tree/main/samples/medtech-service-mappings) provide conforming and valid [device](overview-of-device-mapping.md) and [FHIR&reg; destination](overview-of-fhir-destination-mapping.md) mappings and test device messages. These samples can be used to help with the authoring and troubleshooting of your own MedTech service mappings.
 
diff --git a/articles/healthcare-apis/iot/overview.md b/articles/healthcare-apis/iot/overview.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # What is the MedTech service?
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 The MedTech service is a Platform as a Service (PaaS) within the Azure Health Data Services. The MedTech service enables you to ingest device data, transform it into a unified FHIR&reg; format, and store it in an enterprise-scale, secure, and compliant cloud environment. 
 
diff --git a/articles/healthcare-apis/iot/troubleshoot-errors-deployment.md b/articles/healthcare-apis/iot/troubleshoot-errors-deployment.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Troubleshoot MedTech service deployment errors
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides troubleshooting steps and fixes for MedTech service deployment errors.
 
diff --git a/articles/healthcare-apis/iot/troubleshoot-errors-logs.md b/articles/healthcare-apis/iot/troubleshoot-errors-logs.md
@@ -12,8 +12,7 @@ ms.author: chrupa
 
 # Troubleshoot errors using the MedTech service logs
 
-> [!IMPORTANT]
-> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central. This deprecation process began in May 2025 and is ongoing.
+[!INCLUDE [IoT deprecation](../includes/iot-deprecation.md)]
 
 This article provides troubleshooting steps and fixes for errors found in the MedTech service logs. 
 
