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/develop/authentication-flows-app-scenarios.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
@@ -41,7 +41,7 @@ Applications can be categorized as in the following list:
41
41
-[Protected resources vs. client applications](#protected-resources-vs-client-applications): Some scenarios are about protecting resources like web apps or web APIs. Other scenarios are about acquiring a security token to call a protected web API.
42
42
-[With users or without users](#with-users-or-without-users): Some scenarios involve a signed-in user, but others, like daemon scenarios, don't involve a user.
43
43
-[Single-page, public client, and confidential client applications](#single-page-public-client-and-confidential-client-applications): These types are three large categories of applications. Each is used with different libraries and objects.
44
-
-[Sign-in audience](v2-supported-account-types.md#certain-authentication-flows-dont-support-all-the-account-types): The available authentication flows differ depending on the sign-in audience. Some flows are available only for work or school accounts. And some are available both for work or school accounts and for personal Microsoft accounts. The allowed audience depends on the authentication flows.
44
+
-[Sign-in audience](v2-supported-account-types.md): The available authentication flows differ depending on the sign-in audience. Some flows are available only for work or school accounts. And some are available both for work or school accounts and for personal Microsoft accounts. The allowed audience depends on the authentication flows.
45
45
-[Supported OAuth 2.0 flows](#scenarios-and-supported-authentication-flows): Authentication flows are used to implement the application scenarios that are requesting tokens. There isn't a one-to-one mapping between application scenarios and authentication flows.
46
46
-[Supported platforms](#scenarios-and-supported-platforms-and-languages): Not all application scenarios are available for every platform.
This article explains what accounts types (sometimes named audiences) are supported in applications.
20
+
This article explains what account types (sometimes called *audiences*) are supported in Microsoft identity platform applications.
21
21
22
22
<!-- This section can be in an include for many of the scenarios (SPA, web app signing-in users, protecting a web API, Desktop (depending on the flows), Mobile -->
23
23
24
-
## Supported accounts types in Microsoft Identity platform applications
24
+
## Account types in the public cloud
25
25
26
-
In the Microsoft Azure public Cloud, most types of apps can sign in users with any audience:
26
+
In the Microsoft Azure public cloud, most types of apps can sign in users with any audience:
27
27
28
-
- If you're writing a Line of Business (LOB) application, you can sign in users in your own organization. Such an application is sometimes named **singletenant**.
29
-
- If you're an ISV, you can write an application which signs-in users:
28
+
- If you're writing a line-of-business (LOB) application, you can sign in users in your own organization. Such an application is sometimes called *single-tenant*.
29
+
- If you're an ISV, you can write an application that signsin users:
30
30
31
-
- In any organization. Such an application is named a **multi-tenant** web application. You'll sometimes read that it signs-in users with their work or school accounts.
32
-
- With their work or school or personal Microsoft account.
33
-
- With only personal Microsoft account.
34
-
> [!NOTE]
35
-
> Currently the Microsoft identity platform supports personal Microsoft accounts only by registering an app for **work or school or Microsoft personal accounts**, and then, restrict sign-in in the code for the application by specifying an Azure AD authority, when building the application, such as `https://login.microsoftonline.com/consumers`.
31
+
- In any organization. Such an application is called a *multitenant* web application. You'll sometimes read that it signsin users with their work or school accounts.
32
+
- With their work or school or personal Microsoft accounts.
33
+
- With only personal Microsoft accounts.
34
+
35
+
- If you're writing a business-to-consumer application, you can also sign in users with their social identities, by using Azure Active Directory B2C (Azure AD B2C).
36
36
37
-
- If you're writing a business to consumers application, you can also sign in users with their social identities, using Azure AD B2C.
37
+
## Account type support in authentication flows
38
38
39
-
## Certain authentication flows don't support all the account types
39
+
Some account types can't be used with certain authentication flows. For instance, in desktop, UWP, or daemon applications:
40
40
41
-
Some account types can't be used with certain authentication flows. For instance, in desktop, UWP applications, or daemon applications:
41
+
- Daemon applications can be used only with Azure AD organizations. It doesn't make sense to try to use daemon applications to manipulate Microsoft personal accounts. The admin consent will never be granted.
42
+
- You can use the Integrated Windows Authentication flow only with work or school accounts (in your organization or any organization). Integrated Windows Authentication works with domain accounts, it and requires the machines to be domain joined or Azure AD joined. This flow doesn't make sense for personal Microsoft accounts.
43
+
- The [Resource Owner Password Credentials grant](./v2-oauth-ropc.md) (username/password) can't be used with personal Microsoft accounts. Personal Microsoft accounts require that the user consents to accessing personal resources at each sign-in session. That's why this behavior isn't compatible with non-interactive flows.
44
+
- Device code flow doesn't work with personal Microsoft accounts.
42
45
43
-
- Daemon applications can only be used with Azure Active Directory organizations. It doesn't make sense to attempt to use daemon applications to manipulate Microsoft personal accounts (the admin consent will never be granted).
44
-
- You can only use the Integrated Windows Authentication flow with work or school accounts (in your organization or any organization). Indeed, Integrated Windows Authentication works with domain accounts, and requires the machines to be domain joined or Azure AD joined. This flow doesn't make sense for personal Microsoft Accounts.
45
-
- The [Resource Owner Password Grant](./v2-oauth-ropc.md) (Username/Password), can't be used with personal Microsoft accounts. Indeed, personal Microsoft accounts require that the user consents to accessing personal resources at each sign-in session. That's why, this behavior isn't compatible with non-interactive flows.
46
-
- Device code flow doesn't yet work with personal Microsoft accounts.
46
+
## Account types in national clouds
47
47
48
-
## Supported account types in national clouds
49
-
50
-
Apps can also sign in users in [national clouds](authentication-national-cloud.md). However, Microsoft personal accounts aren't supported in these clouds (by definition of these clouds). That's why the supported account types are reduced, for these clouds, to your organization (single tenant) or any organizations (multi-tenant applications).
48
+
Apps can also sign in users in [national clouds](authentication-national-cloud.md). However, Microsoft personal accounts aren't supported in these clouds. That's why the supported account types are reduced, for these clouds, to your organization (single tenant) or any organizations (multitenant applications).
51
49
52
50
## Next steps
53
51
54
-
- Learn more about [Tenancy in Azure Active Directory](./single-and-multi-tenant-apps.md)
55
-
- Learn more about [National Clouds](./authentication-national-cloud.md)
52
+
- Learn more about [tenancy in Azure Active Directory](./single-and-multi-tenant-apps.md).
53
+
- Learn more about [national clouds](./authentication-national-cloud.md).
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/azure-subscription-service-limits.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
title: Azure subscription limits and quotas
3
3
description: Provides a list of common Azure subscription and service limits, quotas, and constraints. This article includes information on how to increase limits along with maximum values.
Checks if the value is NOT NULL and returns it else returns the alternate. It tests for all inputs until it finds the first non-null value
323
+
Checks if the first parameter is null. If not null, the first parameter is returned. If null, the second parameter is returned. If three parameters are specified, the behavior is the same as iif(isNull(value1), value2, value3) and the third parameter is returned if the first value is not null.
title: Azure Event Grid - Enable diagnostic logs for a topic
2
+
title: Azure Event Grid - Enable diagnostic logs for topics or domains
3
3
description: This article provides step-by-step instructions on how to enable diagnostic logs for an Azure event grid topic.
4
4
services: event-grid
5
5
author: spelluru
6
6
7
7
ms.service: event-grid
8
8
ms.topic: how-to
9
-
ms.date: 01/30/2020
9
+
ms.date: 04/27/2020
10
10
ms.author: spelluru
11
11
---
12
12
13
-
# Diagnostic logs for an Azure event grid topic
14
-
Diagnostic settings allow Event Grid users to capture and view publish and delivery failure Logs in one of the following places: an Azure storage account, an event hub, or a Log Analytics workspace. This article provides step-by-step instructions to enable diagnostic logs for an event grid topic.
13
+
# Enable Diagnostic logs for Azure event grid topics or domains
14
+
Diagnostic Settings now allow Event Grid users to capture and view **publish and delivery failure** Logs in either a Storage account, an event hub, or a Log Analytics Workspace. This article provides step-by-step instructions to enable these settings on an Event Grid Topic.
15
15
16
16
## Prerequisites
17
17
18
18
- A provisioned event grid topic
19
-
- A provisioned destination for capturing diagnostic logs. It can one of the following destinations:
19
+
- A provisioned destination for capturing diagnostic logs. It can one of the following destinations in the same location as the event grid topic:
20
20
- Azure storage account
21
21
- Event hub
22
22
- Log Analytics workspace
23
23
24
-
25
24
## Steps for enabling diagnostic logs for a topic
26
25
26
+
> [!NOTE]
27
+
> The following procedure provides step-by-step instructions for enabling diagnostic logs for a topic. Steps for enabling diagnostic logs for a domain are very similar. In step 2, navigate to the event grid **domain** in the Azure portal.
28
+
27
29
1. Sign in to the [Azure portal](https://portal.azure.com).
28
30
2. Navigate to the event grid topic for which you want to enable diagnostic log settings.
29
31
3. Select **Diagnostic settings** under **Monitoring** in the left menu.
30
32
4. On the **Diagnostic settings** page, select **Add New Diagnostic Setting**.
7. Select the **DeliveryFailures** and **PublishFailures** options in the **Log** section.
37
+
36
38
6. Enable one or more of the capture destinations for the logs, and then configure them by selecting a previous created capture resource.
37
39
- If you select **Archive to a storage account**, select **Storage account - Configure**, and then select the storage account in your Azure subscription.
38
40
@@ -41,13 +43,43 @@ Diagnostic settings allow Event Grid users to capture and view publish and deliv
41
43
42
44
- If you select **Send to Log Analytics**, select the Log Analytics workspace.
43
45
44
-
7. Select the **DeliveryFailures** and **PublishFailures** options in the **Log** section.
45
-
46
-
8. Select **Save**. Select **X** in the right-corner to close the page.
46
+
8. Select **Save**. Then, select **X** in the right-corner to close the page.
47
47
9. Now, back on the **Diagnostic settings** page, confirm that you see a new entry in the **Diagnostics Settings** table.
48
48
49
49
50
50
You can also enable collection of all metrics for the topic.
51
51
52
+
## View diagnostic logs in Azure Storage
53
+
54
+
1. Once you enable a storage account as a capture destination and Event Grid starts emitting diagnostic logs, you should see new containers named **insights-logs-deliveryfailures** and **insights-logs-publishfailures** in the storage account.
55
+
56
+
57
+
2. As you navigate through one of the containers, you will end up at a blob in JSON format. The file contains log entries for either a delivery failure or a publish failure. The navigation path represents the **ResourceId** of the event grid topic and the timestamp (minute level) as to when the log entries were emitted. The blob/JSON file, which is downloadable, in the end adheres to the schema described in the next section.
58
+
59
+
[](./media/enable-diagnostic-logs-topic/select-json.png)
60
+
3. You should see content in the JSON file similar to the following example:
| Time | DateTime | The time when the log entry was generated <p>**Example value:** 01-29-2020 09:52:02.700</p> |
78
+
| EventSubscriptionName | String | The name of the event subscription <p>**Example value:** "EVENTSUB1"</p> <p>This property exists only for delivery failure logs.</p> |
79
+
| Category | String | The log category name. <p>**Example values:** "DeliveryFailures" or "PublishFailures" |
80
+
| OperationName | String | The name of the operation performed while encountering the failure.<p>**Example Values:** "Deliver" for delivery failures. |
81
+
| Message | String | The log message for the user explaining the reason for the failure and other additional details. |
82
+
| ResourceId | String | The resource ID for the topic/domain resource<p>**Example Values:** `/SUBSCRIPTIONS/SAMPLE-SUBSCRIPTION-ID/RESOURCEGROUPS/SAMPLE-RESOURCEGROUP/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/TOPIC1` |
83
+
52
84
## Next steps
53
-
If you need more help, post your issue in the [Stack Overflow forum](https://stackoverflow.com/questions/tagged/azure-eventgrid) or open a [support ticket](https://azure.microsoft.com/support/options/).
85
+
See the following article: [Create diagnostic setting to collect resource logs and metrics in Azure](../azure-monitor/platform/diagnostic-settings.md)
0 commit comments