You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer Lockbox produces two types of audit logs:
122
+
1. Logs that are initiated by Microsoft and correspond to lockbox request being created, expired, or when access sessions end. This set of audit logs do not correspond to a specific user ID since the actions are initiated by Microsoft.
123
+
2. Logs that are initiated by end user actions, such as when a user approves or denies a lockbox request. If the user that performs these operations does not have an E5 license assigned, the logs are filtered out and will not show up in the audit logs.
124
+
125
+
By default, the audit logs are preserved for a duration of one year. You need a 10-Year Audit Log Retention add-on license to retain audit records for 10 years. See [Audit (Premium)](/microsoft-365/compliance/audit-solutions-overview?view=o365-worldwide#audit-premium-1&preserve-view=true) for more details on audit log retention.
126
+
121
127
## Licensing requirements for Customer Lockbox
122
128
123
129
Customer Lockbox policy will be enforced only on environments that are activated for Managed Environments. Managed Environments is included as an entitlement in standalone Power Apps, Power Automate, Power Virtual Agents, Power Pages, and Dynamics 365 licenses that give premium usage rights. To learn more about Managed Environment licensing, see [Licensing](managed-environment-licensing.md) and [Licensing overview for Microsoft Power Platform](pricing-billing-skus.md).
@@ -128,17 +134,20 @@ In addition, access to Customer Lockbox for Microsoft Power Platform and Dynamic
128
134
- Microsoft 365 A5/E5/F5/G5 Compliance
129
135
- Microsoft 365 F5 Security & Compliance
130
136
- Microsoft 365 A5/E5/F5/G5 Insider Risk Management
137
+
- Microsoft 365 A5/E5/F5/G5 Information Protection and Governance
131
138
[Learn more](https://go.microsoft.com/fwlink/?linkid=2214240) about applicable licenses.
132
139
133
140
## Exclusions
134
141
135
-
Lockbox requests aren't triggered in the following engineering support scenarios:
142
+
- Lockbox requests aren't triggered in the following engineering support scenarios:
143
+
144
+
- Emergency scenarios that fall outside of standard operating procedures, such as a major service outage that requires immediate attention to recover or restore services in unexpected or unpredictable cases. These “break glass” events are rare and, in most instances, don't require any access to customer data to resolve.
136
145
137
-
- Emergency scenarios that fall outside of standard operating procedures, such as a major service outage that requires immediate attention to recover or restore services in unexpected or unpredictable cases. These “break glass” events are rare and, in most instances, don't require any access to customer data to resolve.
146
+
- A Microsoft engineer accesses the underlying platform as part of troubleshooting and is inadvertently exposed to customer data. It's rare that such scenarios would result in access to meaningful quantities of customer data.
138
147
139
-
-A Microsoft engineer accesses the underlying platform as part of troubleshooting and is inadvertently exposed to customer data. It's rare that such scenarios would result in access to meaningful quantities of customer data.
148
+
-Customer Lockbox requests are also not triggered by external legal demands for data. For details, refer to the discussion of government requests for data in the [Microsoft Trust Center](https://www.microsoft.com/trust-center/).
140
149
141
-
Customer Lockbox requests are also not triggered by external legal demands for data. For details, refer to the discussion of government requests for data in the [Microsoft Trust Center](https://www.microsoft.com/trust-center/).
150
+
-Customer Lockbox won't apply to the access and manual review of customer data shared for Copilot AI features. Customer Lockbox will remain enabled for all in-scope data.
**Service Performance** report provides details of all standard and custom connectors to understand performance bottlenecks and client versus service API issues. An environment admin will get insights into:
56
+
**Service Performance** report provides details of all standard and custom connectors to understand performance bottlenecks and client versus service API issues. An environment admin gets insights into:
57
57
58
58
- Connectors used in the environment.
59
59
- Best and least performant service and the API service response times.
@@ -62,18 +62,18 @@ There are six reports available for Power Apps admins. The last viewed environme
62
62
- The number of HTTP 500 error codes of connectors indicating issues around the server not responding to calls from the client.
63
63
- The number of successful connection requests.
64
64
65
-
All the service performance KPI's can be filtered with attributes like a specific service or connector, device platform, player version, and country, state, or city to drill down into the specific API.
65
+
All the service performance KPIs can be filtered with attributes like a specific service or connector, device platform, player version, and country, state, or city to drill down into the specific API.
66
66
67
67
> [!div class="mx-imgBorder"]
68
68
> ![Power Apps analytics service performance report.](media/powerapps-analytics-service-performance.png"Power Apps analytics service performance report")
69
69
70
-
**Connectors report** provides visibility into the standard and custom connectors being used by canvas apps. The last 28 days of data is visible at the environment level.
70
+
**Connectors report** provides visibility into the standard and custom connectors being used by canvas apps. The last 28 days of data are visible at the environment level.
71
71
72
-
Admins can gain insights into the number of connectors associated with each app, the specific connectors being used by each app, and the owner of the connector. It also provides data on the number of times the app has been shared, the number of app sessions, and the last accessed time for visibility into high usage apps and connectors.
72
+
Admins can gain insights into the number of connectors associated with each app, the specific connectors being used by each app, and the owner of the connector. It also provides data on the number of times the app has been shared, the number of app sessions, and the last accessed time for visibility into high usage apps and connectors. At this time, this functionality is limited to only connections that the admin owns, and only activity on those specific connections.
73
73
74
-
**A sample scenario**: An admin can gain insight into the number of shares and usage of a specific finance app using one or more connectors. This will allow the admin to engage with the app owner to ensure no sensitive data is inadvertently being shared through the app.
74
+
**A sample scenario**: An admin can gain insight into the number of shares and usage of a specific finance app using one or more connectors. This allows the admin to engage with the app owner to ensure no sensitive data is inadvertently being shared through the app.
75
75
76
-
Note that the current iteration of this specific report does not have a download report feature.
76
+
The current iteration of this specific report does not have a download report feature.
Copy file name to clipboardExpand all lines: power-platform/admin/associate-email-address.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ description: Associate an email address with a row.
4
4
author: DanaMartens
5
5
ms.component: pa-admin
6
6
ms.topic: conceptual
7
-
ms.date: 11/5/2021
7
+
ms.date: 05/05/2023
8
8
ms.subservice: admin
9
9
ms.author: dmartens
10
-
ms.reviewer: jimholtz
10
+
ms.reviewer: sericks
11
11
search.audienceType:
12
12
- admin
13
13
---
@@ -29,7 +29,8 @@ When customer engagement apps track an email, it associates the email address to
29
29
If the email address resolves to more than 100 rows, the **From** field will not be associated to a row and appears as unresolved.
30
30
31
31
> [!NOTE]
32
-
> The only exception is when the owner of the mailbox or queue tracking the email is the owner of the duplicated row. A row that's owned by you takes precedence over any rows that you don't own. For example, if the email address exists in a contact and account table and the mailbox owner also owns the account but not the contact, the **From** field will resolve to the account.
32
+
> - The only exception is when the owner of the mailbox or the queue tracking the email is the owner of the duplicated row. A row that's owned by you takes precedence over any rows that you don't own. For example, if the email address exists in a contact and account table and the mailbox owner also owns the account but not the contact, the **From** field will resolve to the account.
33
+
> - When an email is tracked immediately by an app, such as Dynamics 365 App for Outlook, the list of records which may be associated are limited to those which the user can access. However, if the email is created by Server-Side Sync, the creation of the email is performed by the SYSTEM account which has access to all records.
33
34
34
35
In the email **To** field, all of the rows of email-enabled tables with the email address will be listed.
0 commit comments