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
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-faq.yml
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -174,4 +174,8 @@ sections:
174
174
What are the differences between monitoring an IoT Central application in the Azure portal and using the audit logs within in IoT Central application.
175
175
answer: |
176
176
Monitoring in the Azure portal is useful for operations monitoring. The audit log in an IoT Central application lets you see who made changes to entities within the the application.
177
+
- question: |
178
+
Can I extend the audit log to store more than 30 days of data?
179
+
answer: |
180
+
Currently, you can't store more tha 30 days of data in the audit log. Entries older than 30 days are deleted automatically.
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-manage-users-roles.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Manage users and roles in Azure IoT Central application | Microsoft Docs
3
3
description: As an administrator, how to manage users and roles in your Azure IoT Central application
4
4
author: dominicbetts
5
5
ms.author: dobett
6
-
ms.date: 06/22/2022
6
+
ms.date: 08/01/2022
7
7
ms.topic: how-to
8
8
ms.service: iot-central
9
9
services: iot-central
@@ -218,6 +218,16 @@ When you define a custom role, you choose the set of permissions that a user is
218
218
| Manage | None |
219
219
| Full Control | Manage |
220
220
221
+
**Audit log permissions**
222
+
223
+
| Name | Dependencies |
224
+
| ---- | -------- |
225
+
| View | None |
226
+
| Full Control | View |
227
+
228
+
> [!CAUTION]
229
+
> Any user granted permission to view the audit log can see all log entries even if they don't have permission to view or modify the entities listed in the log. Therefore, any user who can view the log can view the identity of and changes made to any modified entity.
Copy file name to clipboardExpand all lines: articles/iot-central/core/howto-use-audit-logs.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,42 +36,42 @@ The log records changes to the following IoT Central entities:
36
36
37
37
The log records changes made by the following types of user:
38
38
39
-
- IoT Central user - the log shows the users email.
39
+
- IoT Central user - the log shows the user's email.
40
40
- API token - the log shows the token name.
41
-
- Azure Active Directory user - the log shows the user email or Id.
41
+
- Azure Active Directory user - the log shows the user email or ID.
42
42
- Service principal - the log shows the service principal name.
43
43
44
44
The log stores data for 30 days, after which it's no longer available.
45
45
46
46
The following screenshot shows the audit log view with the location of the sorting and filtering controls highlighted:
47
47
48
-
<!-- TODO: Add a screenshot -->
48
+
:::image type="content" source="media/howto-use-audit-logs/audit-log.png" alt-text="Screenshot that shows the audit log. The location of the sort and filter controls is highlighted.":::
49
+
50
+
## Customize the log
51
+
52
+
Select **Column options** to customize the audit log view. You can add and remove columns, reorder the columns, and change the column widths:
53
+
54
+
:::image type="content" source="media/howto-use-audit-logs/audit-logs-column-options.png" alt-text="Screenshot that shows the audit log column options.":::
49
55
50
56
## Sort the log
51
57
52
58
You can sort the log into ascending or descending timestamp order. To sort, select **Timestamp**:
53
59
54
-
<!-- TODO: Add a screenshot -->
60
+
:::image type="content" source="media/howto-use-audit-logs/audit-logs-sorting.png" alt-text="Screenshot that shows how to sort the log into descending timestamp order.":::
55
61
56
62
## Filter the log
57
63
58
64
To focus on a specific time, filter the log by time range. Select **Edit time range** and specify the range you're interested in:
59
65
60
-
<!-- TODO: Add a screenshot -->
66
+
:::image type="content" source="media/howto-use-audit-logs/audit-logs-time.png" alt-text="Screenshot that shows how filter the log to show the last hour of entries.":::
61
67
62
68
To focus on specific entries, filter by entity type or action. Select **Filter** and use the multi-select drop-downs to specify your filter conditions:
63
69
64
-
<!-- TODO: Add a screenshot -->
65
-
66
-
## Customize the log
67
-
68
-
Select **Column options** to customize the audit log view. You can add and remove columns, reorder the columns, and change the column widths:
69
-
70
-
<!-- TODO: Add a screenshot -->
70
+
:::image type="content" source="media/howto-use-audit-logs/audit-logs-filter.png" alt-text="Screenshot that shows how filter the log to show only updates to user entities.":::
71
71
72
72
## Manage access
73
73
74
-
The built-in **App Administrator** role has access to the audit logs by default. The administrator can grant access to other roles, To learn more, see [Manage users and roles in your IoT Central application](howto-manage-users-roles.md).
74
+
The built-in **App Administrator** role has access to the audit logs by default. The administrator can grant access to other roles. An administrator can assign either **Full control** or **View** audit log permissions to other roles. To learn more, see [Manage users and roles in your IoT Central application](howto-manage-users-roles.md).
75
75
76
76
> [!IMPORTANT]
77
77
> Any user granted permission to view the audit log can see all log entries even if they don't have permission to view or modify the entities listed in the log. Therefore, any user who can view the log can view the identity of and changes made to any modified entity.
Copy file name to clipboardExpand all lines: articles/iot-central/core/overview-iot-central-admin.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,13 +86,13 @@ An administrator can:
86
86
87
87
To learn more, see [Create and use a custom application template](howto-create-iot-central-application.md#create-and-use-a-custom-application-template).
88
88
89
-
## Integrate with DevOps pipelines
89
+
## Integrate with Azure Pipelines
90
90
91
-
Continuous integration and continuous delivery (CI/CD) refers to the process of developing and delivering software in short, frequent cycles using automation pipelines. You can use Azure DevOps pipelines to automate the build, test, and deployment of IoT Central application configurations.
91
+
Continuous integration and continuous delivery (CI/CD) refers to the process of developing and delivering software in short, frequent cycles using automation pipelines. You can use Azure Pipelines to automate the build, test, and deployment of IoT Central application configurations.
92
92
93
93
Just as IoT Central is a part of your larger IoT solution, make IoT Central a part of your CI/CD pipeline.
94
94
95
-
To learn more, see [Integrate IoT Central into your Azure DevOps CI/CD pipeline](howto-integrate-with-devops.md).
95
+
To learn more, see [Integrate IoT Central into your Azure CI/CD pipeline](howto-integrate-with-devops.md).
0 commit comments