Skip to content

Commit 236d1c0

Browse files
authored
Merge branch 'main' into nov-hdi-freshness
2 parents 4716067 + 35e574b commit 236d1c0

File tree

5 files changed

+33
-11
lines changed

5 files changed

+33
-11
lines changed

articles/backup/backup-client-automation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ $CredsFilename = Get-AzRecoveryServicesVaultSettingsFile -Backup -Vault $Vault1
139139
In the latest Az module of PowerShell, because of underlying platform limitations, downloading the vault credentials requires a self-signed certificate. The following example shows how to provide a self-signed certificate and download the vault credentials.
140140

141141
```powershell
142-
$dt = $(Get-Date).ToString("M-d-yyyy")
142+
143143
$cert = New-SelfSignedCertificate -CertStoreLocation Cert:\CurrentUser\My -FriendlyName 'test-vaultcredentials' -subject "Windows Azure Tools" -KeyExportPolicy Exportable -NotAfter $(Get-Date).AddHours(48) -NotBefore $(Get-Date).AddHours(-24) -KeyProtection None -KeyUsage None -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.2") -Provider "Microsoft Enhanced Cryptographic Provider v1.0"
144144
$certficate = [convert]::ToBase64String($cert.Export([System.Security.Cryptography.X509Certificates.X509ContentType]::Pfx))
145145
$CredsFilename = Get-AzRecoveryServicesVaultSettingsFile -Backup -Vault $Vault -Path $CredsPath -Certificate $certficate

articles/expressroute/metro.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: expressroute
55
author: duongau
66
ms.service: azure-expressroute
77
ms.topic: conceptual
8-
ms.date: 06/03/2024
8+
ms.date: 11/24/2024
99
ms.author: duau
1010
ms.custom: references_regions, ai-usage
1111
---
@@ -40,9 +40,9 @@ The following diagram allows for a comparison between the standard ExpressRoute
4040

4141
| Metro location | Peering locations | Location address | Zone | Local Azure Region | ER Direct | Service Provider |
4242
|--|--|--|--|--|--|--|
43-
| Amsterdam Metro | Amsterdam<br>Amsterdam2 | Equinix AM5<br>Digital Realty AMS8 | 1 | West Europe | &check; | Colt<sup>1</sup><br>Console Connect<sup>1</sup><br>Digital Realty<br>Equinix<br>euNetworks<br><br>Megaport<br> |
44-
| Singapore Metro | Singapore<br>Singapore2 | Equinix SG1<br>Global Switch Tai Seng | 2 | Southeast Asia | &check; | Console Connect<sup>1</sup><br>Equinix<br>Megaport |
45-
| Zurich Metro | Zurich<br>Zurich2 | Digital Realty ZUR2<br>Equinix ZH5 | 1 | Switzerland North | &check; | Colt<sup>1</sup><br>Digital Realty |
43+
| Amsterdam Metro | Amsterdam<br>Amsterdam2 | Equinix AM5<br>Digital Realty AMS8 | 1 | West Europe | &check; | Colt<br>Digital Realty<br>Equinix<br>euNetworks<br><br>Megaport<br> |
44+
| Singapore Metro | Singapore<br>Singapore2 | Equinix SG1<br>Global Switch Tai Seng | 2 | Southeast Asia | &check; | Colt<br>Equinix<br>Megaport |
45+
| Zurich Metro | Zurich<br>Zurich2 | Digital Realty ZUR2<br>Equinix ZH5 | 1 | Switzerland North | &check; | Colt<br>Digital Realty |
4646

4747
<sup>1<sup> These service providers will be available in the future.
4848

articles/hdinsight/configure-azure-blob-storage.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,22 @@ Same thing can be achieved via ARM request if that is how you want to create HDI
8282
8383
}
8484
```
85-
85+
86+
## MSI based Script Action using primary Azure Blob Storage storage
87+
88+
Previously while adding the primary storage as Azure Blob Storage storage in the Azure HDInsight cluster, you can't provide MSI for authentication.
89+
Also to access a script action that isn't accessible anonymously, you need to mention the SAS Key in the script action parameters, so the Azure HDInsight Cluster can access the script for execution.
90+
91+
Now, you can add Azure Blob Storage storage in Azure HDInsight cluster as a primary storage using MSI.
92+
93+
Hence there's no need to provide the SAS key in the script action parameters, while adding the script action, if the script uploaded to the primary Azure Blob Storage storage account.
94+
95+
The script is downloaded and implemented. This will work even if the script isn't publicly accessible.
96+
97+
The new feature specifically supports scripts that aren't publicly accessible but don't require a SAS key or token. This provides an additional layer of security for scripts that need to be kept private.
98+
99+
The conventional script action in which is anonymously accessible or if a SAS key is passed along with the script URI, still works without any changes. For more information, see [Customize Azure HDInsight clusters by using script actions](./hdinsight-hadoop-customize-cluster-linux.md)
100+
86101
## Next steps
87102
88103
* [Use Azure Data Lake Storage Gen2 with Azure HDInsight clusters](./hdinsight-managed-identities.md)

articles/sentinel/resource-context-rbac.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: cwatson
1212

1313
# Manage access to Microsoft Sentinel data by resource
1414

15-
Typically, users who have access to a Log Analytics workspace enabled for Microsoft Sentinel also have access to all the workspace data, including security content. Administrators can use [Azure roles](roles.md) to configure access to specific features in Microsoft Sentinel, depending on the access requirements in their team.
15+
Access to a workspace is managed by using Azure RBAC. Typically, users who have access to a Log Analytics workspace enabled for Microsoft Sentinel also have access to all the workspace data, including security content. Administrators can use [Azure roles](roles.md) to configure access to specific features in Microsoft Sentinel, depending on the access requirements in their team.
1616

1717
However, you may have some users who need to access only specific data in your workspace, but shouldn't have access to the entire Microsoft Sentinel environment. For example, you may want to provide a non-security operations (non-SOC) team with access to the Windows event data for the servers they own.
1818

@@ -154,6 +154,10 @@ The following list describes scenarios where other solutions for data access may
154154

155155

156156

157-
## Next steps
157+
## Related content
158158

159-
For more information, see [Permissions in Microsoft Sentinel](roles.md).
159+
For more information, see:
160+
161+
- [Permissions in Microsoft Sentinel](roles.md)
162+
- [Manage access to Log Analytics workspaces](/azure/azure-monitor/logs/manage-access)
163+
- [What is Azure role-based access control (Azure RBAC)?](/azure/role-based-access-control/overview)

articles/virtual-network-manager/concept-event-logs.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,11 +100,11 @@ This category emits one log per connectivity configuration change per virtual ne
100100
| time | Datetime when the event was logged. |
101101
| resourceId | Resource ID of the network manager. |
102102
| location | Location of the virtual network resource. |
103-
| operationName | Operation that resulted in the virtual network being added or removed. Always the Microsoft.Network/networkManagers/connectivityConfigurations/write operation. |
103+
| operationName | Operation that resulted in the virtual network being added or removed. |
104104
| category | Category of this log. Always ConnectivityConfigurationChange. |
105105
| resultType | Indicates successful or failed operation. |
106106
| correlationId | GUID that can help relate or debug logs. |
107-
| level | Always Info. |
107+
| level | Info or Warning. |
108108
| properties | Collection of properties of the log. |
109109

110110
Within the `properties` attribute are several nested attributes:
@@ -115,6 +115,9 @@ Within the `properties` attribute are several nested attributes:
115115
| TargetResourceIds | Resource ID of the virtual network that experienced a change in connectivity configuration application. |
116116
| Message | A static message stating if the connectivity configuration change was successful or unsuccessful. |
117117

118+
> [!NOTE]
119+
> Connectivity configuration allows virtual networks with overlapping IP spaces within the same connected group, but communication to an overlapped IP address is dropped. In addition, when a connected group’s VNet is peered with an external VNet (a VNet not in the connected group) that has overlapping address spaces, these overlapping address spaces become inaccessible within the connected group. Traffic from the peered VNet to the overlapping address spaces is routed to the external VNet, while traffic from other VNets in the connected group to the overlapping address spaces is dropped. Logs will show a "Warning" level, with the `TargetResourceIds` field indicating the IDs of VNets with overlapping address spaces and a `message` indicating that either complete or partial address spaces are inaccessible due to overlapping addresses.
120+
118121
Within the `AppliedConnectivityConfigurations` attribute are several nested attributes:
119122

120123
| AppliedConnectivityConfigurations attributes | Description |

0 commit comments

Comments
 (0)