Merge branch 'MicrosoftDocs:main' into main

Author: jacinda-eng

articles/azure-monitor/app/java-jmx-metrics-configuration.md

@@ -2,7 +2,7 @@
 title: How to configure JMX metrics - Azure Monitor application insights for Java
 description: Configure extra JMX metrics collection for Azure Monitor Application Insights Java agent
 ms.topic: conceptual
-ms.date: 03/16/2021
+ms.date: 05/13/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ms.reviewer: mmcc

articles/azure-monitor/app/java-standalone-telemetry-processors-examples.md

@@ -2,7 +2,7 @@
 title: Telemetry processor examples - Azure Monitor Application Insights for Java
 description: Explore examples that show telemetry processors in Azure Monitor Application Insights for Java.
 ms.topic: conceptual
-ms.date: 12/29/2020
+ms.date: 05/13/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ms.reviewer: mmcc

articles/azure-monitor/app/java-standalone-telemetry-processors.md

@@ -2,7 +2,7 @@
 title: Telemetry processors (preview) - Azure Monitor Application Insights for Java
 description: Learn to configure telemetry processors in Azure Monitor Application Insights for Java.
 ms.topic: conceptual
-ms.date: 10/29/2020
+ms.date: 05/13/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ms.reviewer: mmcc

articles/azure-monitor/app/usage-flows.md

@@ -2,7 +2,7 @@
 title: Application Insights User Flows analyzes navigation flows
 description: Analyze how users move between the pages and features of your web app.
 ms.topic: conceptual
-ms.date: 07/30/2021
+ms.date: 05/13/2023
 ms.reviewer: mmcc
 ---
 

articles/azure-monitor/app/usage-heart.md

@@ -2,8 +2,8 @@
 title: HEART analytics workbook
 description: Product teams can use the HEART workbook to measure success across five user-centric dimensions to deliver better software.
 ms.topic: conceptual
-ms.date: 11/11/2021
-ms.reviewer: mmccgit
+ms.date: 05/13/2023
+ms.reviewer: mmcc
 ---
 
 # Analyze product usage with HEART

articles/communication-services/toc.yml

@@ -326,16 +326,14 @@ items:
         href: concepts/analytics/insights/chat-insights.md
       - name: Export SDK telemetry to Application Insights
         href: quickstarts/telemetry-application-insights.md
-    - name: Phone calling
+  - name: Phone calling
+    items:
+    - name: Add emergency calling to your app
+      href: quickstarts/telephony/emergency-calling.md
+    - name: Phone numbers
       items:
-      - name: Add emergency calling to your app
-        href: quickstarts/telephony/emergency-calling.md
-      - name: Validate a domain for direct routing
-        href: how-tos/telephony/domain-validation.md
-      - name: Phone numbers
-        items:
-        - name: Port a phone number into Azure
-          href: quickstarts/telephony/port-phone-number.md
+      - name: Port a phone number into Azure
+        href: quickstarts/telephony/port-phone-number.md
     - name: Call Automation
       items:
       - name: Build a workflow for customer interactions 

articles/cost-management-billing/manage/ea-transfers.md

@@ -58,7 +58,7 @@ When you request to transfer an old enterprise enrollment to a new enrollment, t
 
 - Usage transferred may take up to 72 hours to be reflected in the new enrollment.
 - If department administrator (DA) or account owner (AO) view charges were enabled on the old transferred enrollment, they must be enabled on the new enrollment.
-- If you're using API reports or Power BI, generate a new API key under your new enrollment.
+- If you're using API reports or Power BI, [generate a new API access key](enterprise-rest-apis.md#api-key-generation) under your new enrollment. For API use, the API access key is used for authentication to older enterprise APIs that are retiring. For more information about retiring APIs that use the API access key, see [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs overview](../automate/migrate-ea-reporting-arm-apis-overview.md).
     - All APIs use either the old enrollment or the new one, not both, for reporting purposes. If you need reports from APIs for the old and new enrollments, you must create your own reports.
 - All Azure services, subscriptions, accounts, departments, and the entire enrollment structure, including all EA department administrators, transfer to a new target enrollment.
 - The enrollment status is set to `Transferred` for the old enrollment. The old enrollment that was transferred is available for historic usage reporting purposes only.

articles/energy-data-services/how-to-manage-audit-logs.md

@@ -0,0 +1,95 @@
+---
+title: How to manage audit logs for Microsoft Azure Data Manager for Energy Preview
+description: Learn how to use audit logs on Azure Data Manager for Energy Preview
+author: sandeepchads
+ms.author: sancha
+ms.service: energy-data-services    
+ms.topic: how-to
+ms.date: 04/11/2023
+ms.custom: template-how-to
+#Customer intent: As a developer, I want to use audit logs to check audit trail for data plane APIs for Azure Data Manager for Energy Preview.
+---
+
+
+# Manage audit logs  
+Audit logs provide auditing trails for data plane APIs on Azure Data Manager for Energy. With audit logs, you can tell:
+* Who performed an action
+* What was the action
+* When was the action performed
+* Status of the action
+
+For example, when you “Add a new member” to the ```users.datalake.admins``` entitlement group using entitlements API, you're able to see this information in audit logs. 
+
+[![Screenshot of audit logs for entitlement](media/how-to-manage-audit-logs/how-to-manage-audit-logs-4-entilements.png)](media/how-to-manage-audit-logs/how-to-manage-audit-logs-4-entilements.png#lightbox)
+ 
+## Enable audit logs
+To enable audit logs in diagnostic logging, select your Azure Data Manager for Energy instance in the Azure portal.
+* Select the **Activity log** screen, and then select **Diagnostic settings**.
+* Select **+ Add diagnostic setting**.
+* Enter the Diagnostic settings name.
+* Select **Audit Events** as the Category. 
+
+[![Screenshot of audit events option in diagnostic settings](media/how-to-manage-audit-logs/how-to-manage-audit-logs-1-audit-event-diagnostic-logs.png)](media/how-to-manage-audit-logs/how-to-manage-audit-logs-1-audit-event-diagnostic-logs.png#lightbox)
+
+* Select appropriate Destination details for accessing the diagnostic logs. 
+ 
+> [!NOTE]
+> It might take up to 15 minutes for the first Logs to show in Log Analytics. 
+For information on how to work with diagnostic logs, see [Azure Resource Log documentation.](../azure-monitor/essentials/platform-logs-overview.md)
+
+## Audit log details
+The audit logs for Azure Data Manager for Energy service returns the following fields.
+
+|Field Name| 	  Type| 	Description|
+|----------|----------|----------------| 
+| TenantID |	String |	The tenant of your Azure Data Manager for Energy instance.|
+| TimeGenerated | UTC format |	The time of the audit log. |
+| Category 	| String | The diagnostic settings category to which the logs belong.|
+| Location | 	string | 	Location of the Azure Data Manager for Energy resource.  |
+| ServiceName 	| String |  	Name of OSDU service running in Azure Data Manager for Energy. For example: Partition, Search, Indexer, Legal, Entitlements, Workflow, Register, Unit, Crs-catalog, File, Schema, and Dataset |
+| OperationName | 	String  |Operation ID or operation name associated to data plane APIs, which emits audit logs for example "Add member" |
+| Data partition ID | 	String |  	Data partition ID on which operation is performed. |
+| Action  |	String | 	Action refers to the type of operation that is, whether it's create, delete, update etc.|
+| ActionID | 	String 	| ID associated with operation. |
+| PuID |	String	| ObjectId of the user in Azure AD|
+| ResultType |	String 	| Define success or failure of operation | 
+| Operation Description	| String |	Provides specific details of the response. These details can include tracing information, such as the symptoms, of the result that are used for further analysis. |
+| RequestId | 	 String 	| This is the unique ID associated to the request, which triggered the operation on data plane. |
+| Message |	String |	Provides message associated with the success or failure of the operation.|
+| ResourceID | 	String | 	The Azure Data Manager for Energy resource ID of the customer under which the audit log belongs. |
+
+## Sample queries
+
+Basic Application Insights queries you can use to explore your log data.
+
+1. Run the following query to group operations by ServiceName:
+
+```sql
+OEPAuditLogs
+| summarize count() by ServiceName
+```
+
+[![Screenshot of key vault, key, user assigned identity, and CMK on encryption tab](media/how-to-manage-audit-logs/how-to-manage-audit-logs-3-allservices.png)](media/how-to-manage-audit-logs/how-to-manage-audit-logs-3-allservices.png#lightbox)
+ 
+2. Run the following query to see the 100 most recent logs:
+
+```sql
+OEPAuditLogs
+| limit 100
+```
+
+3. Run the following query to get all the failed results:
+
+```sql
+OEPAuditLogs
+| where ResultType contains "Failure"
+```
+
+
+## Next steps
+
+Learn about Managed Identity:
+> [!div class="nextstepaction"]
+> [Managed Identity in Azure Data Manager for Energy Preview](how-to-use-managed-identity.md)
+
+

articles/energy-data-services/index.yml

@@ -111,4 +111,6 @@ landingContent:
           - text: Set up use Managed Identity
             url: how-to-use-managed-identity.md
           - text: Enable resource sharing (CORS)
-            url: how-to-enable-cors.md
+            url: how-to-enable-cors.md
+          - text: Set up audit logs
+            url: how-to-manage-audit-logs.md