Merge pull request MicrosoftDocs#42291 from barclayn/azlog-dates

changing the dates back at Sunil's request

Author: PRMerger10

articles/security/security-azure-log-integration-ad.md

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ums.workload: na
-ms.date: 05/24/2018
+ms.date: 05/25/2018
 ms.author: barclayn
 ms.custom: azlog
 
@@ -22,9 +22,6 @@ ms.custom: azlog
 
 Azure Active Directory (Azure AD) audit events help you identify privileged actions that occurred in Azure Active Directory. You can see the types of events that you can track by reviewing [Azure Active Directory audit report events](/active-directory/active-directory-reporting-audit-events#list-of-audit-report-events.md).
 
->[!IMPORTANT]
-> The Azure Log integration feature will be deprecated by 12/15/2018.  Please read about this in the [Introduction to Azure Log Integration](security-azure-log-integration-overview.md) topic before proceeding.
-
 ## Steps to integrate Azure Active Directory audit logs
 
 > [!NOTE]

articles/security/security-azure-log-integration-faq.md

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload8: na
-ms.date: 05/24/2018
+ms.date: 05/25/2018
 ms.author: barclayn
 ms.custom: azlog
 
@@ -22,9 +22,6 @@ ms.custom: azlog
 
 This article answers frequently asked questions (FAQ) about Azure Log Integration.
 
->[!IMPORTANT]
-> The Azure Log integration feature will be deprecated by 12/15/2018.  Please read about this in the [Introduction to Azure Log Integration](security-azure-log-integration-overview.md) topic before proceeding.
-
 Azure Log Integration is a Windows operating system service that you can use to integrate raw logs from your Azure resources into your on-premises security information and event management (SIEM) systems. This integration provides a unified dashboard for all your assets, on-premises or in the cloud. You can then aggregate, correlate, analyze, and alert for security events associated with your applications.
 
 The preferred method for integrating Azure logs is by using your SIEM vendor’s Azure Monitor connector and following these [instructions](../monitoring-and-diagnostics/monitor-stream-monitoring-data-event-hubs.md). However, if your SIEM vendor doesn’t provide a connector to Azure Monitor, you may be able to use Azure Log Integration as a temporary solution (if your SIEM is supported by Azure Log Integration) until such a connector is available.

articles/security/security-azure-log-integration-get-started.md

@@ -13,16 +13,13 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ums.workload: na
-ms.date: 05/24/2018
+ms.date: 05/25/2018
 ms.author: barclayn
 ms.custom: azlog
 
 ---
 # Azure Log Integration with Azure Diagnostics logging and Windows event forwarding
 
->[!IMPORTANT]
-> The Azure Log integration feature will be deprecated by 12/15/2018.  Please read about this in the [Introduction to Azure Log Integration](security-azure-log-integration-overview.md) topic before proceeding.
-
 You should only use Azure log integration if an [Azure Monitor](../monitoring-and-diagnostics/monitoring-get-started.md) connector isn't available from your Security Incident and Event Management (SIEM) vendor.
 
 Azure Log Integration makes Azure logs available to your SIEM so you can create a unified security dashboard for all your assets.

articles/security/security-azure-log-integration-keyvault-eventhub.md

@@ -17,9 +17,6 @@ ms.custom: AzLog
 
 You can use Azure Log Integration to retrieve logged events and make them available to your security information and event management (SIEM) system. This tutorial shows an example of how Azure Log Integration can be used to process logs that are acquired through Azure Event Hubs.
 
->[!IMPORTANT]
-> The Azure Log integration feature will be deprecated by 12/15/2018.
-
 The preferred method for integrating Azure logs is by using your SIEM vendor’s Azure Monitor connector and following these [instructions](../monitoring-and-diagnostics/monitor-stream-monitoring-data-event-hubs.md). However, if your SIEM vendor doesn’t provide a connector to Azure Monitor, you may be able to use Azure Log Integration as a temporary solution (if your SIEM is supported by Azure Log Integration) until such a connector is available.
 
 

articles/security/security-azure-log-integration-overview.md

@@ -13,19 +13,16 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 05/24/2018
+ms.date: 05/25/2018
 ms.author: TomSh
 ms.custom: azlog
 
 ---
 # Introduction to Azure Log Integration
 
->[!IMPORTANT]
-> The Azure Log Integration feature will be deprecated by 12/15/2018.
-
 Azure Log Integration was made available to simplify the task of integrating Azure logs with your on-premises Security Information and Event Management (SIEM) system.
 
-New downloads are being disabled by 6/15/2018 but Azure will continue to support existing installations until 12/15/2018. The recommended method for integrating Azure logs is to use your SIEM vendor’s connectors. Azure Monitor provides the ability to stream the logs into event hubs, and SIEM vendors can write connectors to further integrate logs from the event hub into the SIEM.  For a description of how this works, follow the instructions in [Monitor stream monitoring for data event hubs](../monitoring-and-diagnostics/monitor-stream-monitoring-data-event-hubs.md). The article also lists the SIEMs for which direct Azure connectors are already available.  
+ The recommended method for integrating Azure logs is to use your SIEM vendor’s connectors. Azure Monitor provides the ability to stream the logs into event hubs, and SIEM vendors can write connectors to further integrate logs from the event hub into the SIEM.  For a description of how this works, follow the instructions in [Monitor stream monitoring for data event hubs](../monitoring-and-diagnostics/monitor-stream-monitoring-data-event-hubs.md). The article also lists the SIEMs for which direct Azure connectors are already available.  
 
 > [!IMPORTANT]
 > If your primary interest is collecting virtual machine logs, most SIEM vendors include this option in their solution. Using the SIEM vendor's connector is always the preferred alternative.