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/active-directory/users-groups-roles/directory-assign-admin-roles.md
+48-4Lines changed: 48 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ The following administrator roles are available:
88
88
[Intune](https://docs.microsoft.com/intune/role-based-access-control) | View all Intune audit data
89
89
[Cloud App Security](https://docs.microsoft.com/cloud-app-security/manage-admins) | Has read-only permissions and can manage alerts<br>Can create and modify file policies and allow file governance actions<br> Can view all the built-in reports under Data Management
90
90
91
-
<!--* **[Compliance Data Administrator](#compliance-data-administrator)**: Users with this role have permissions to protect and track data in the Microsoft 365 compliance center, Microsoft 365 admin center, and Azure. Users can also manage all features within the Exchange admin center, Compliance Manager, and Teams & Skype for Business admin center and create support tickets for Azure and Microsoft 365.
91
+
***[Compliance Data Administrator](#compliance-data-administrator)**: Users with this role have permissions to protect and track data in the Microsoft 365 compliance center, Microsoft 365 admin center, and Azure. Users can also manage all features within the Exchange admin center, Compliance Manager, and Teams & Skype for Business admin center and create support tickets for Azure and Microsoft 365.
92
92
93
93
In | Can do
94
94
----- | ----------
@@ -97,7 +97,7 @@ The following administrator roles are available:
97
97
[Office 365 Security & Compliance Center](https://support.office.com/article/About-Office-365-admin-roles-da585eea-f576-4f55-a1e0-87090b6aaa9d) | Manage data governance<br>Perform legal and data investigation<br>Manage Data Subject Request
98
98
[Intune](https://docs.microsoft.com/intune/role-based-access-control) | View all Intune audit data
99
99
[Cloud App Security](https://docs.microsoft.com/cloud-app-security/manage-admins) | Has read-only permissions and can manage alerts<br>Can create and modify file policies and allow file governance actions<br> Can view all the built-in reports under Data Management
100
-
-->
100
+
101
101
***[Conditional Access Administrator](#conditional-access-administrator)**: Users with this role have the ability to manage Azure Active Directory conditional access settings.
102
102
> [!NOTE]
103
103
> To deploy Exchange ActiveSync conditional access policy in Azure, the user must also be a Global Administrator.
@@ -208,7 +208,7 @@ Additionally, the user can access reports related to adoption & usage of Kaizala
208
208
[Azure Security Center](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles) | Can view security policies, view security states, edit security policies, view alerts and recommendations, dismiss alerts and recommendations
209
209
[Office 365 service health](https://docs.microsoft.com/office365/enterprise/view-service-health) | View the health of Office 365 services
210
210
211
-
<!--* **[Security operator](#security-operator)**: Users with this role can manage alerts and have global read-only access on security-related feature, including all information in Microsoft 365 security center, Azure Active Directory, Identity Protection, Privileged Identity Management, as well as the ability to read Azure Active Directory sign-in reports and audit logs, and in Office 365 Security & Compliance Center.
211
+
***[Security operator](#security-operator)**: Users with this role can manage alerts and have global read-only access on security-related feature, including all information in Microsoft 365 security center, Azure Active Directory, Identity Protection, Privileged Identity Management and Office 365 Security & Compliance Center. More information about Office 365 permissions is available at [Permissions in the Office 365 Security & Compliance Center](https://docs.microsoft.com/en-us/office365/securitycompliance/permissions-in-the-security-and-compliance-center).
212
212
213
213
In | Can do
214
214
--- | ---
@@ -220,7 +220,8 @@ Additionally, the user can access reports related to adoption & usage of Kaizala
220
220
[Intune](https://docs.microsoft.com/intune/role-based-access-control) | All permissions of the Security Reader role
221
221
[Cloud App Security](https://docs.microsoft.com/cloud-app-security/manage-admins) | All permissions of the Security Reader role
222
222
[Office 365 service health](https://docs.microsoft.com/office365/enterprise/view-service-health) | View the health of Office 365 services
223
-
-->
223
+
<!--* **[Security Operator](#security-operator)**: Users with this role can manage alerts and have global read-only access on security-related feature, including all information in Microsoft 365 security center, Azure Active Directory, Identity Protection, Privileged Identity Management.-->
224
+
224
225
***[Security Reader](#security-reader)**: Users with this role have global read-only access on security-related feature, including all information in Microsoft 365 security center, Azure Active Directory, Identity Protection, Privileged Identity Management, as well as the ability to read Azure Active Directory sign-in reports and audit logs, and in Office 365 Security & Compliance Center. More information about Office 365 permissions is available at [Permissions in the Office 365 Security & Compliance Center](https://support.office.com/article/Permissions-in-the-Office-365-Security-Compliance-Center-d10608af-7934-490a-818e-e68f17d0e9c1).
225
226
226
227
In | Can do
@@ -563,6 +564,28 @@ Can read and manage compliance configuration and reports in Azure AD and Office
563
564
| microsoft.office365.skypeForBusiness/allEntities/allTasks | Manage all aspects of Skype for Business Online. |
564
565
| microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Office 365 support tickets. |
565
566
567
+
### Compliance Data Administrator
568
+
Creates and manages compliance content.
569
+
570
+
> [!NOTE]
571
+
> This role has additional permissions outside of Azure Active Directory. For more information, see role description above.
572
+
>
573
+
>
574
+
575
+
|**Actions**|**Description**|
576
+
| --- | --- |
577
+
| microsoft.aad.cloudAppSecurity/allEntities/allTasks | Read and configure Microsoft Cloud App Security. |
578
+
| microsoft.azure.informationProtection/allEntities/allTasks | Manage all aspects of Azure Information Protection. |
579
+
| microsoft.azure.serviceHealth/allEntities/allTasks | Read and configure Azure Service Health. |
580
+
| microsoft.azure.supportTickets/allEntities/allTasks | Create and manage Azure support tickets. |
581
+
| microsoft.office365.webPortal/allEntities/basic/read | Read basic properties on all resources in microsoft.office365.webPortal. |
582
+
| microsoft.office365.complianceManager/allEntities/allTasks | Manage all aspects of Office 365 Compliance Manager |
583
+
| microsoft.office365.exchange/allEntities/allTasks | Manage all aspects of Exchange Online. |
584
+
| microsoft.office365.serviceHealth/allEntities/allTasks | Read and configure Office 365 Service Health. |
585
+
| microsoft.office365.sharepoint/allEntities/allTasks | Create and delete all resources, and read and update standard properties in microsoft.office365.sharepoint. |
586
+
| microsoft.office365.skypeForBusiness/allEntities/allTasks | Manage all aspects of Skype for Business Online. |
587
+
| microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Office 365 support tickets. |
588
+
566
589
### Conditional Access Administrator
567
590
Can manage conditional access capabilities.
568
591
@@ -1079,6 +1102,25 @@ Can read security information and reports, and manage configuration in Azure AD
1079
1102
| microsoft.office365.protectionCenter/allEntities/update | Update all resources in microsoft.office365.protectionCenter. |
1080
1103
| microsoft.office365.serviceHealth/allEntities/allTasks | Read and configure Office 365 Service Health. |
1081
1104
1105
+
### Security Operator
1106
+
Creates and manages security events.
1107
+
1108
+
> [!NOTE]
1109
+
> This role has additonal permissions outside of Azure Active Directory. For more information, see role description above.
1110
+
>
1111
+
>
1112
+
1113
+
|**Actions**|**Description**|
1114
+
| --- | --- |
1115
+
| microsoft.aad.cloudAppSecurity/allEntities/allTasks | Read and configure Microsoft Cloud App Security. |
1116
+
| microsoft.aad.identityProtection/allEntities/read | Read all resources in microsoft.aad.identityProtection. |
1117
+
| microsoft.aad.privilegedIdentityManagement/allEntities/read | Read all resources in microsoft.aad.privilegedIdentityManagement. |
1118
+
| microsoft.azure.advancedThreatProtection/allEntities/read | Read and configure Azure AD Advanced Threat Protection. |
1119
+
| microsoft.intune/allEntities/allTasks | Manage all aspects of Intune. |
Copy file name to clipboardExpand all lines: articles/aks/configure-kubenet.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The following basic calculations compare the difference in network models:
58
58
59
59
### Virtual network peering and ExpressRoute connections
60
60
61
-
To provide on-premises connectivity, both *kubenet* and *Azure-CNI* network approaches can use [Azure virtual network peering][vnet-peering] or [ExpressRoute connections][express-route]. Plan your IP address ranges carefully to prevent overlap and incorrect traffic routing. For example, many on-premises networks use a *10.0.0.0/8* address range that is advertised over the ExpressRoute connection. It's recommended to create your AKS clusters into Azure virtual network subnets outside of this address range, such as *172.26.0.0/16*.
61
+
To provide on-premises connectivity, both *kubenet* and *Azure-CNI* network approaches can use [Azure virtual network peering][vnet-peering] or [ExpressRoute connections][express-route]. Plan your IP address ranges carefully to prevent overlap and incorrect traffic routing. For example, many on-premises networks use a *10.0.0.0/8* address range that is advertised over the ExpressRoute connection. It's recommended to create your AKS clusters into Azure virtual network subnets outside of this address range, such as *172.16.0.0/16*.
62
62
63
63
### Choose a network model to use
64
64
@@ -88,15 +88,15 @@ To get started with using *kubenet* and your own virtual network subnet, first c
88
88
az group create --name myResourceGroup --location eastus
89
89
```
90
90
91
-
If you don't have an existing virtual network and subnet to use, create these network resources using the [az network vnet create][az-network-vnet-create] command. In the following example, the virtual network is named *myVnet* with the address prefix of *10.0.0.0/8*. A subnet is created named *myAKSSubnet* with the address prefix *10.240.0.0/16*.
91
+
If you don't have an existing virtual network and subnet to use, create these network resources using the [az network vnet create][az-network-vnet-create] command. In the following example, the virtual network is named *myVnet* with the address prefix of *192.168.0.0/16*. A subnet is created named *myAKSSubnet* with the address prefix *192.168.1.0/24*.
92
92
93
93
```azurecli-interactive
94
94
az network vnet create \
95
95
--resource-group myResourceGroup \
96
96
--name myAKSVnet \
97
-
--address-prefixes 10.0.0.0/8 \
97
+
--address-prefixes 192.168.0.0/16 \
98
98
--subnet-name myAKSSubnet \
99
-
--subnet-prefix 10.240.0.0/16
99
+
--subnet-prefix 192.168.1.0/24
100
100
```
101
101
102
102
## Create a service principal and assign permissions
@@ -146,7 +146,7 @@ The following IP address ranges are also defined as part of the cluster create p
146
146
147
147
* The *--pod-cidr* should be a large address space that isn't in use elsewhere in your network environment. This range includes any on-premises network ranges if you connect, or plan to connect, your Azure virtual networks using Express Route or a Site-to-Site VPN connection.
148
148
* This address range must be large enough to accommodate the number of nodes that you expect to scale up to. You can't change this address range once the cluster is deployed if you need more addresses for additional nodes.
149
-
* The pod IP address range is used to assign a */24* address space to each node in the cluster. In the following example, the *--pod-cidr* of *192.168.0.0/16* assigns the first node *192.168.0.0/24*, the second node *192.168.1.0/24*, and the third node *192.168.2.0/24*.
149
+
* The pod IP address range is used to assign a */24* address space to each node in the cluster. In the following example, the *--pod-cidr* of *10.244.0.0/16* assigns the first node *10.244.0.0/24*, the second node *10.244.1.0/24*, and the third node *10.244.2.0/24*.
150
150
* As the cluster scales or upgrades, the Azure platform continues to assign a pod IP address range to each new node.
151
151
152
152
* The *--docker-bridge-address* lets the AKS nodes communicate with the underlying management platform. This IP address must not be within the virtual network IP address range of your cluster, and shouldn't overlap with other address ranges in use on your network.
Copy file name to clipboardExpand all lines: articles/app-service/operating-system-functionality.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ It is important to monitor your disk utilization as your application grows. If t
61
61
62
62
- The app may throw an error indicating not enough space on the disk.
63
63
- You may see disk errors when browsing to the Kudu console.
64
-
- Deployment from VSTS or Visual Studio may fail with `ERROR_NOT_ENOUGH_DISK_SPACE: Web deployment task failed. (Web Deploy detected insufficient space on disk)`.
64
+
- Deployment from Azure DevOps or Visual Studio may fail with `ERROR_NOT_ENOUGH_DISK_SPACE: Web deployment task failed. (Web Deploy detected insufficient space on disk)`.
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ You can use any of the commands listed at [Redis commands](https://redis.io/comm
247
247
*`redis-cli -h <Azure Cache for Redis name>.redis.cache.windows.net -a <key>`
248
248
249
249
> [!NOTE]
250
-
> The Redis command-line tools do not work with the SSL port, but you can use a utility such as `stunnel` to securely connect the tools to the SSL port by following the directions in the [Announcing ASP.NET Session State Provider for Redis Preview Release](https://blogs.msdn.com/b/webdev/archive/2014/05/12/announcing-asp-net-session-state-provider-for-redis-preview-release.aspx) blog post.
250
+
> The Redis command-line tools do not work with the SSL port, but you can use a utility such as `stunnel` to securely connect the tools to the SSL port by following the directions in the [How to use the Redis command-line tool with Azure Cache for Redis](https://docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-how-to-redis-cli-tool) article.
Copy file name to clipboardExpand all lines: articles/azure-government/documentation-government-services-monitoringandmanagement.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,7 +158,9 @@ For more information on using PowerShell, see [public documentation](../azure-mo
158
158
## Application Insights
159
159
160
160
> [!NOTE]
161
-
> Codeless agent/extension based monitoring for Azure App Services is **currently not supported**. Snapshot Debugger is also not currently available in Azure Government. As soon as this functionality becomes available this article will be updated.
161
+
> Codeless agent/extension based monitoring for Azure App Services is **currently not supported**. As soon as this functionality becomes available this article will be updated.
162
+
163
+
This section describes the supplemental configuration that is required to use Application Insights in Azure Government. To learn more about Azure Monitor and Application Insights checkout the [full documentation](https://docs.microsoft.com/azure/azure-monitor/overview).
162
164
163
165
### Enable Application Insights for ASP.NET & ASP.NET Core with Visual Studio
164
166
@@ -173,6 +175,10 @@ Currently for Azure Government customers, the only way to enable Application Ins
173
175
174
176
3. Make the appropriate Application Insights SDK endpoint modifications for either [ASP.NET](https://docs.microsoft.com/azure/azure-government/documentation-government-services-monitoringandmanagement#net-with-applicationinsightsconfig) or [ASP.NET Core](https://docs.microsoft.com/azure/azure-government/documentation-government-services-monitoringandmanagement#net-core) depending on your project type.
175
177
178
+
### Snapshot Debugger
179
+
180
+
Snapshot Debugger is now available for Azure Government customers. To use Snapshot Debugger the only additional prerequisite is to insure that you are using [Snapshot Collector version 1.3.5](https://www.nuget.org/packages/Microsoft.ApplicationInsights.SnapshotCollector/1.3.5-pre-1906.403) or later. Then simply follow the standard [Snapshot Debugger documentation](https://docs.microsoft.com/azure/azure-monitor/app/snapshot-debugger).
181
+
176
182
### SDK endpoint modifications
177
183
178
184
In order to send data from Application Insights to the Azure Government region, you will need to modify the default endpoint addresses that are used by the Application Insights SDKs. Each SDK requires slightly different modifications.
Copy file name to clipboardExpand all lines: articles/azure-maps/how-to-request-real-time-data.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,9 +110,9 @@ Let's use "522" as our metro ID, which is the metro ID for "Seattle–Tacoma–B
110
110
}
111
111
112
112
113
-
## Real-time availability and vacancy information for bike docking station
113
+
## Real-time data for bike docking station
114
114
115
-
The [Get Transit Dock Info API](https://aka.ms/AzureMapsMobilityTransitDock) of the Azure Maps Mobility Service, allows to request static and real-time information for a given bike or scooter docking station. We will make a request to get real-time data for a docking station for bikes.
115
+
The [Get Transit Dock Info API](https://aka.ms/AzureMapsMobilityTransitDock) of the Azure Maps Mobility Service, allows to request static and real-time information such as availability and vacancy information for a given bike or scooter docking station. We will make a request to get real-time data for a docking station for bikes.
116
116
117
117
In order to make a request to the Get Transit Dock Info API, you will need the **dockId** for that station. You can get the dock ID by making a search request to the [Get Nearby Transit API](https://aka.ms/AzureMapsMobilityNearbyTransit) and setting the **objectType** parameter to "bikeDock". Follow the steps below to get real-time data of a docking station for bikes.
0 commit comments