Skip to content

Commit 15145f6

Browse files
authored
Merge pull request #301017 from MicrosoftDocs/main
Publish to live, Sunday 4 AM PST, 6/8
2 parents 04df1b9 + 1dad453 commit 15145f6

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

articles/frontdoor/origin-security.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,10 @@ You should configure your origin to disallow traffic that doesn't come through P
3535
- Azure Storage provides a firewall, which you can use to deny traffic from the internet. For more information, see [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
3636
- Internal load balancers with Azure Private Link service aren't publicly routable. You can also configure network security groups to ensure that you disallow access to your virtual network from the internet.
3737

38+
## Managed Identities
39+
40+
Managed identities provided by Microsoft Entra ID enables your Front Door instance to securely access other Microsoft Entra protected resources, such as Azure Blob Storage, without the need to manage credentials. After you enable managed identity for Front Door and granting the managed identity necessary permissions to your origin, Front Door will use the managed identity to obtain an access token from Microsoft Entra ID for accessing the specified resource. After successfully obtaining the token, Front Door will set the value of the token in the Authorization header using the Bearer scheme and then forward the request to the origin. Front Door caches the token until it expires. For more information, see [use managed identities to authenticate to origins (preview)](origin-authentication-with-managed-identities.md).
41+
3842
::: zone-end
3943

4044
## Public IP address-based origins

articles/sentinel/connect-threat-intelligence-tip.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.collection: usx-security
1919
# Connect your threat intelligence platform to Microsoft Sentinel
2020

2121
> [!NOTE]
22-
> This data connector is on a path for deprecation. More information will be published on the precise timeline. Use the new Threat Intelligence Upload Indicators API data connector for new solutions going forward.
22+
> This data connector will be deprecated and will stop collecting data in **April 2026**. We recommend transitioning to the new Threat Intelligence Upload Indicators API data connector as soon as possible to ensure uninterrupted data collection.
2323
> For more information, see [Connect your threat intelligence platform to Microsoft Sentinel with the upload API](connect-threat-intelligence-upload-api.md).
2424
2525
Many organizations use threat intelligence platform (TIP) solutions to aggregate threat indicator feeds from various sources. From the aggregated feed, the data is curated to apply to security solutions such as network devices, EDR/XDR solutions, or security information and event management (SIEM) solutions such as Microsoft Sentinel. By using the TIP data connector, you can use these solutions to import threat indicators into Microsoft Sentinel.

0 commit comments

Comments
 (0)