Skip to content

Commit 0614a38

Browse files
authored
Merge pull request #255483 from MicrosoftDocs/main
10/18/2023 PM Publish
2 parents 3ffa915 + edff1ae commit 0614a38

File tree

789 files changed

+5324
-1596
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

789 files changed

+5324
-1596
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6378,6 +6378,11 @@
63786378
"source_path_from_root": "/articles/azure-monitor/app/separate-resources.md",
63796379
"redirect_url": "/azure/azure-monitor/app/create-workspace-resource#how-many-application-insights-resources-should-i-deploy",
63806380
"redirect_document_id": false
6381+
},
6382+
{
6383+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-app-dashboards.md",
6384+
"redirect_url": "/azure/azure-monitor/app/overview-dashboard#create-custom-kpi-dashboards-using-application-insights",
6385+
"redirect_document_id": false
63816386
}
63826387
]
63836388
}

articles/active-directory-b2c/analytics-with-application-insights.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -323,6 +323,6 @@ To disable Application Insights logs, change the `DisableTelemetry` metadata to
323323

324324
## Next steps
325325

326-
Learn how to [create custom KPI dashboards using Azure Application Insights](../azure-monitor/app/tutorial-app-dashboards.md).
326+
Learn how to [create custom KPI dashboards using Azure Application Insights](../azure-monitor/app/overview-dashboard.md#create-custom-kpi-dashboards-using-application-insights).
327327

328328
::: zone-end

articles/active-directory-b2c/index-web-app.yml

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,3 @@ landingContent:
5050
url: enable-authentication-in-node-web-app-options.md
5151
- text: Python
5252
url: enable-authentication-python-web-app-options.md
53-
- title: "Sample"
54-
linkLists:
55-
- linkListType: sample
56-
links:
57-
- text: Java
58-
url: https://github.com/Azure-Samples/ms-identity-msal-java-samples/tree/main/1.%20Server-Side%20Scenarios/msal-b2c-web-sample

articles/active-directory-b2c/partner-saviynt.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.subservice: B2C
1818

1919
Learn to integrate Azure Active Directory B2C (Azure AD B2C) with the Saviynt Security Manager platform, which has visibility, security, and governance. Saviynt incorporates application risk and governance, infrastructure management, privileged account management, and customer risk analysis.
2020

21-
Learn more: [Saviynt for Azure AD B2C](https://saviynt.com/integrations/azure-ad/for-b2c/)
21+
Learn more: [Saviynt for Azure AD B2C](https://saviynt.com/integrations/old-version-azure-ad/for-b2c/)
2222

2323
Use the following instructions to set up access control delegated administration for Azure AD B2C users. Saviynt determines if a user is authorized to manage Azure AD B2C users with:
2424

@@ -46,7 +46,7 @@ The Saviynt integration includes the following components:
4646
* **Azure AD B2C** – identity as a service for custom control of customer sign-up, sign-in, and profile management
4747
* See, [Azure AD B2C, Get started](https://azure.microsoft.com/services/active-directory/external-identities/b2c/)
4848
* **Saviynt for Azure AD B2C** – identity governance for delegated administration of user life-cycle management and access governance
49-
* See, [Saviynt for Azure AD B2C](https://saviynt.com/integrations/azure-ad/for-b2c/)
49+
* See, [Saviynt for Azure AD B2C](https://saviynt.com/integrations/old-version-azure-ad/for-b2c/)
5050
* **Microsoft Graph API** – interface for Saviynt to manage Azure AD B2C users and their access
5151
* See, [Use the Microsoft Graph API](/graph/use-the-api)
5252

articles/active-directory/architecture/resilience-with-monitoring-alerting.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,17 +47,17 @@ For example, track the following metrics, since a sudden drop in either will lea
4747

4848
- **Previous period**: Create temporal charts to show changes in the Total requests and Success rate (%) over some previous period for reference purposes, for example, last week.
4949

50-
- **Alerting**: Using log analytics define [alerts](/azure/azure-monitor/alerts/alerts-create-new-alert-rule) that get triggered when there are sudden changes in the key indicators. These changes may negatively impact the SLOs. Alerts use various forms of notification methods including email, SMS, and webhooks. Start by defining a criterion that acts as a threshold against which alert will be triggered. For example:
50+
- **Alerting**: Using log analytics define [alerts](/azure/azure-monitor/alerts/alerts-create-new-alert-rule) that get triggered when there are sudden changes in the key indicators. These changes might negatively impact the SLOs. Alerts use various forms of notification methods including email, SMS, and webhooks. Start by defining a criterion that acts as a threshold against which alert will be triggered. For example:
5151
- Alert against abrupt drop in Total requests: Trigger an alert when number of total requests drop abruptly. For example, when there's a 25% drop in the total number of requests compared to previous period, raise an alert.
5252
- Alert against significant drop in Success rate (%): Trigger an alert when success rate of the selected policy significantly drops.
5353
- Upon receiving an alert, troubleshoot the issue using [Log Analytics](/azure/azure-monitor/visualize/workbooks-view-designer-conversion-overview), [Application Insights](/azure/active-directory-b2c/troubleshoot-with-application-insights), and [VS Code extension](https://marketplace.visualstudio.com/items?itemName=AzureADB2CTools.aadb2c) for Azure AD B2C. After you resolve the issue and deploy an updated application or policy, it continues to monitor the key indicators until they return back to normal range.
5454

5555
- **Service alerts**: Use the [Azure AD B2C service level alerts](/azure/service-health/service-health-overview) to get notified of service issues, planned maintenance, health advisory, and security advisory.
5656

5757
- **Reporting**: [By using log analytics](../reports-monitoring/howto-integrate-activity-logs-with-azure-monitor-logs.md), build reports that help you gain understanding about user insights, technical challenges, and growth opportunities.
58-
- **Health Dashboard**: Create [custom dashboards using Azure Dashboard](/azure/azure-monitor/app/tutorial-app-dashboards) feature, which supports adding charts using Log Analytics queries. For example, identify pattern of successful and failed sign-ins, failure reasons and telemetry about devices used to make the requests.
58+
- **Health Dashboard**: Create [custom dashboards using Azure Dashboard](../../azure-monitor/app/overview-dashboard.md#create-custom-kpi-dashboards-using-application-insights) feature, which supports adding charts using Log Analytics queries. For example, identify pattern of successful and failed sign-ins, failure reasons and telemetry about devices used to make the requests.
5959
- **Abandon Azure AD B2C journeys**: Use the [workbook](https://github.com/azure-ad-b2c/siem#list-of-abandon-journeys) to track the list of abandoned Azure AD B2C journeys where user started the sign-in or sign-up journey but never finished it. It provides you details about policy ID and breakdown of steps that are taken by the user before abandoning the journey.
60-
- **Azure AD B2C monitoring workbooks**: Use the [monitoring workbooks](https://github.com/azure-ad-b2c/siem) that include Azure AD B2C dashboard, Multi-factor authentication (MFA) operations, Conditional Access report, and Search logs by correlationId. This practice provides better insights into the health of your Azure AD B2C environment.
60+
- **Azure AD B2C monitoring workbooks**: Use the [monitoring workbooks](https://github.com/azure-ad-b2c/siem) that include Azure AD B2C dashboard, Multifactor authentication (MFA) operations, Conditional Access report, and Search logs by correlationId. This practice provides better insights into the health of your Azure AD B2C environment.
6161

6262
## Next steps
6363

articles/active-directory/authentication/concept-authentication-passwordless.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 09/15/2022
9+
ms.date: 10/18/2023
1010

1111
ms.author: justinha
1212
author: justinha
@@ -23,7 +23,7 @@ Features like multifactor authentication (MFA) are a great way to secure your or
2323
| --- | --- | --- |
2424
| Passwordless | Windows 10 Device, phone, or security key | Biometric or PIN |
2525

26-
Each organization has different needs when it comes to authentication. Microsoft global Azure and Azure Government offer the following three passwordless authentication options that integrate with Microsoft Entra ID:
26+
Each organization has different needs when it comes to authentication. Microsoft Global Azure and Azure Government offer the following three passwordless authentication options that integrate with Microsoft Entra ID:
2727

2828
- Windows Hello for Business
2929
- Microsoft Authenticator
@@ -87,7 +87,7 @@ Users can register and then select a FIDO2 security key at the sign-in interface
8787

8888
FIDO2 security keys can be used to sign in to their Microsoft Entra ID or Microsoft Entra hybrid joined Windows 10 devices and get single-sign on to their cloud and on-premises resources. Users can also sign in to supported browsers. FIDO2 security keys are a great option for enterprises who are very security sensitive or have scenarios or employees who aren't willing or able to use their phone as a second factor.
8989

90-
We have a reference document for which [browsers support FIDO2 authentication with Microsoft Entra ID](fido2-compatibility.md), as well as best practices for developers wanting to [support FIDO2 auth in the applications they develop](../develop/support-fido2-authentication.md).
90+
We have a reference document for which [browsers support FIDO2 authentication with Microsoft Entra ID](fido2-compatibility.md), and best practices for developers wanting to [support FIDO2 auth in the applications they develop](../develop/support-fido2-authentication.md).
9191

9292
![Sign in to Microsoft Edge with a security key](./media/concept-authentication-passwordless/concept-web-sign-in-security-key.png)
9393

@@ -184,6 +184,14 @@ The following considerations apply:
184184

185185
- Users may not register passwordless credentials within a tenant where they are a guest, the same way that they do not have a password managed in that tenant.
186186

187+
## Unsupported scenarios
188+
189+
We recommend no more than 20 sets of keys for each passwordless method for any user account. As more keys are added, the user object size increases, and you may notice degradation for some operations. In that case, you should remove unnecessary keys. For more information and the PowerShell cmdlets to query and remove keys, see
190+
[Using WHfBTools PowerShell module for cleaning up orphaned Windows Hello for Business Keys](https://support.microsoft.com/topic/using-whfbtools-powershell-module-for-cleaning-up-orphaned-windows-hello-for-business-keys-779d1f3f-bb2d-c495-0f6b-9aeb940eeafb). The topic uses **/UserPrincipalName** optional parameter to query only keys for a specific user. The permissions required are to run as an administrator or the specified user.
191+
192+
When you use PowerShell to create a CSV file with all of the existing keys, carefully identify the keys that you need to keep, and remove those rows from the CSV. Then use the modified CSV with PowerShell to delete the remaining keys to bring the account key count under the limit.
193+
194+
It is safe to delete any key reported as "Orphaned"="True" in the CSV. An orphaned key is one for a device that is not longer registered in Entra ID. If removing all Orphans still doesn't bring the User account below the limit it is necessary to look at the "DeviceId" and "CreationTime" columns to identify which keys to target for deletion. Be careful to remove any row in the CSV for keys you want to keep. Keys for any DeviceID corresponding to devices the user actively uses should be removed from the CSV before the deletion step.
187195

188196
## Choose a passwordless method
189197

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -331,6 +331,11 @@ A nudge won't appear if a user is presented with the [terms of use (ToU)](../con
331331

332332
A nudge won't appear if a user is redirected during sign-in due to [Conditional Access custom controls](../conditional-access/controls.md) settings.
333333

334+
**Are there any plans to discontinue SMS and Voice as methods usable for MFA?**
335+
336+
No, there are no such plans.
337+
334338
## Next steps
335339

336340
[Enable passwordless sign-in with Microsoft Authenticator](howto-authentication-passwordless-phone.md)
341+

articles/active-directory/devices/manage-device-identities.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,9 @@ To view or copy BitLocker keys, you need to be the owner of the device or have o
106106
- Intune Service Administrator
107107
- Security Administrator
108108
- Security Reader
109+
110+
> [!NOTE]
111+
> When devices that utilize [Windows Autopilot](/mem/autopilot/windows-autopilot) are reused, **and there is a new device owner**, that new device owner must contact an administrator to acquire the BitLocker recovery key for that device. Administrative unit scoped administrators will lose access to BitLocker recovery keys after device ownership changes. These scoped administrators will need to contact a non-scoped administrator for the recovery keys.
109112
110113
## View and filter your devices
111114

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
title: 'Microsoft Entra ID licensing'
3+
description: This article documents licensing requirements for Microsoft Entra ID features.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: barclayn
7+
manager: amycolannino
8+
editor: ''
9+
ms.service: active-directory
10+
ms.topic: conceptual
11+
ms.tgt_pltfrm: na
12+
ms.workload: identity
13+
ms.date: 09/21/2023
14+
ms.subservice: hybrid
15+
ms.author: barclayn
16+
---
17+
18+
# Microsoft Entra ID licensing
19+
20+
This article discusses Microsoft Entra services' licensing. It is intended for IT decision makers, IT administrators, and IT professionals who are considering Microsoft Entra services for their organizations. This article isn't intended for end users.
21+
22+
>[!IMPORTANT]
23+
> For licensing information on services not listed here, refer to the service's documentation or the [Azure Active Directory pricing page.](https://azure.microsoft.com/pricing/details/active-directory/)
24+
25+
26+
## App provisioning
27+
28+
[!INCLUDE [App provisioning](../includes/licensing-app-provisioning.md)]
29+
30+
## Authentication
31+
32+
[!INCLUDE [Authentication](../includes/licensing-authentication.md)]
33+
34+
## Microsoft Entra Connect
35+
36+
[!INCLUDE [Information about free tier services](../includes/licensing-free-license.md)]
37+
38+
## Microsoft Entra Connect health
39+
40+
[!INCLUDE [Services available in the P1](../includes/licensing-p1-license.md)]
41+
42+
## Microsoft Entra Conditional Access
43+
44+
[!INCLUDE [Microsoft Entra Conditional access](../includes/licensing-conditional-access.md)]
45+
46+
## Microsoft Entra ID Governance
47+
48+
[!INCLUDE [Microsoft Entra ID Governance](../includes/licensing-governance.md)]
49+
50+
## Microsoft Entra ID Protection
51+
52+
[!INCLUDE [Microsoft Entra ID Protection](../includes/licensing-identity-protection.md)]
53+
54+
## Managed identities
55+
56+
[!INCLUDE [Managed identities](../includes/licensing-managed-identities.md)]
57+
58+
## Multi-tenant organizations
59+
60+
[!INCLUDE [Multi-tenant organizations](../includes/licensing-multi-tenant-organizations.md)]
61+
62+
## Microsoft Entra Privileged Identity management
63+
64+
[!INCLUDE [Microsoft Entra Privileged Identity](../includes/licensing-pim.md)]
65+
66+
## Role based access control
67+
68+
[!INCLUDE [Roles based access control](../includes/licensing-role-based-access-control.md)]
69+
70+
### Roles
71+
72+
[!INCLUDE [licensing-roles](../includes/licensing-roles.md)]
73+
74+
## Microsoft Entra reporting and monitoring
75+
76+
[!INCLUDE [Microsoft Entra reporting and monitoring](../includes/licensing-reports-monitoring.md)]
77+
78+
## Microsoft Entra Verified ID
79+
80+
[!INCLUDE [Microsoft Entra Verified ID](../includes/licensing-verified-id.md)]
81+
82+
## Features in preview
83+
84+
[!INCLUDE [features-preview](../includes/licensing-features-preview.md)]
85+
86+
## Next steps
87+
88+
- [Azure AD pricing](https://azure.microsoft.com/pricing/details/active-directory/)
89+
- [Azure AD B2C pricing](https://azure.microsoft.com/pricing/details/active-directory-b2c/)
90+
- [Microsoft Entra Plans & Pricing](https://www.microsoft.com/en-us/security/business/microsoft-entra-pricing?rtc=1)
91+

articles/active-directory/fundamentals/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,8 @@ items:
6565
href: licensing-whatis-azure-portal.md
6666
- name: Microsoft Entra ID preview program terms
6767
href: licensing-preview-terms.md
68+
- name: Microsoft Entra ID licensing
69+
href: licensing.md
6870
- name: Sign up for Microsoft Entra ID P1 or P2
6971
href: get-started-premium.md
7072
- name: Quick security wins

0 commit comments

Comments
 (0)