Skip to content

Commit fbae12a

Browse files
committed
fix bugs
1 parent e40d93a commit fbae12a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-monitor/platform/private-link-security.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ With Private Link you can:
2222
- Stop data exfiltration from your networks by only authorizing access to specific resources, and block access to all destinations
2323
- Securely connect your private on-premises network to Azure Monitor using ExpressRoute and Private Link
2424

25-
For more information, see [Key Benefits of Private Link](../../private-link/private-link-overview#key-benefits.md)
25+
For more information, see [Key Benefits of Private Link](../../private-link/private-link-overview.md#key-benefits)
2626

2727
## How it works
2828

@@ -145,7 +145,7 @@ First, you can connect this Application Insights resource to Azure Monitor Priva
145145
Second, you can control how this resource can be reached from outside of the private link scopes listed above.
146146
If you set **Allow public network access for ingestion** to **No**, then machines or SDKs outside of the connected scopes cannot upload data to this component. If you set **Allow public network access for queries** to **No**, then machines outside of the scopes cannot access data in this workspace. That data includes access to dashboards, query API, insights in the Azure portal, and more.
147147

148-
Restricting access in this manner only applies to data in the workspace. Configuration changes, including turning these access settings on or off, are managed by Azure Resource Manager. You should restrict access to Resource Manager using the appropriate roles, permissions, network controls, and auditing. For more information, see [Azure Monitor Roles, Permissions, and Security](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/roles-permissions-security).
148+
Restricting access in this manner only applies to data in the workspace. Configuration changes, including turning these access settings on or off, are managed by Azure Resource Manager. You should restrict access to Resource Manager using the appropriate roles, permissions, network controls, and auditing. For more information, see [Azure Monitor Roles, Permissions, and Security](roles-permissions-security.md).
149149

150150
## Using customer-owned storage accounts for log ingestion
151151

0 commit comments

Comments
 (0)