Skip to content

Commit 0b189b2

Browse files
2 parents 44b09c5 + 884230e commit 0b189b2

File tree

110 files changed

+3075
-961
lines changed

Some content is hidden

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

110 files changed

+3075
-961
lines changed

.openpublishing.redirection.azure-productivity.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,6 +144,11 @@
144144
"source_path": "articles/lab-services/quick-create-lab-template.md",
145145
"redirect_url": "/azure/lab-services/how-to-create-lab-template",
146146
"redirect_document_id": true
147+
},
148+
{
149+
"source_path": "articles/lab-services/classroom-labs-faq.yml",
150+
"redirect_url": "/azure/lab-services/lab-services-overview",
151+
"redirect_document_id": false
147152
}
148153
]
149154
}

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -809,6 +809,11 @@
809809
"source_path_from_root": "/articles/defender-for-cloud/faq-azure-monitor-logs.yml",
810810
"redirect_url": "/azure/defender-for-cloud/faq-data-collection-agents",
811811
"redirect_document_id": true
812+
},
813+
{
814+
"source_path_from_root": "/articles/defender-for-cloud/defender-for-storage-exclude.md",
815+
"redirect_url": "/azure/defender-for-cloud/defender-for-storage-classic-enable#exclude-a-storage-account-from-a-protected-subscription-in-the-per-transaction-plan",
816+
"redirect_document_id": true
812817
}
813818
]
814819
}

articles/active-directory/develop/active-directory-optional-claims.md

Lines changed: 16 additions & 16 deletions
Large diffs are not rendered by default.

articles/active-directory/develop/includes/console-app/quickstart-python.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: develop
99
ms.topic: include
1010
ms.workload: identity
11-
ms.date: 01/10/2022
11+
ms.date: 03/28/2023
1212
ms.author: owenrichards
1313
ms.reviewer: jmprieur
1414
ms.custom: aaddev, identityplatformtop40, devx-track-python, "scenarios:getting-started", "languages:Python", mode-other
@@ -74,7 +74,7 @@ If you try to run the application at this point, you'll receive *HTTP 403 - Forb
7474

7575
##### Global tenant administrator
7676

77-
If you are a global tenant administrator, go to **API Permissions** page in **App registrations** in the Azure portal and select **Grant admin consent for {Tenant Name}** (Where {Tenant Name} is the name of your directory).
77+
If you're a global tenant administrator, go to **API Permissions** page in **App registrations** in the Azure portal and select **Grant admin consent for {Tenant Name}** (Where {Tenant Name} is the name of your directory).
7878

7979

8080
##### Standard user
@@ -87,8 +87,7 @@ https://login.microsoftonline.com/Enter_the_Tenant_Id_Here/adminconsent?client_i
8787

8888
Where:
8989
* `Enter_the_Tenant_Id_Here` - replace this value with the **Tenant Id** or **Tenant name** (for example, contoso.microsoft.com)
90-
* `Enter_the_Application_Id_Here` - is the **Application (client) ID** for the application you registered.
91-
90+
* `Enter_the_Application_Id_Here` - is the **Application (client) ID** for the application you registered previously.
9291

9392

9493
#### Step 5: Run the application

articles/active-directory/reports-monitoring/concept-all-sign-ins.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.topic: conceptual
99
ms.workload: identity
1010
ms.subservice: report-monitor
11-
ms.date: 03/24/2023
11+
ms.date: 03/28/2023
1212
ms.author: sarahlipsey
1313
ms.reviewer: besiler
1414
ms.collection: M365-identity-device-management
@@ -142,7 +142,8 @@ Sign-ins are aggregated in the non-interactive users when the following data mat
142142
- Status
143143
- Resource ID
144144

145-
The IP address of non-interactive sign-ins doesn't match the actual source IP of where the refresh token request is coming from. Instead, it shows the original IP used for the original token issuance.
145+
> [!NOTE]
146+
> The IP address of non-interactive sign-ins performed by [confidential clients](../develop/msal-client-applications.md) doesn't match the actual source IP of where the refresh token request is coming from. Instead, it shows the original IP used for the original token issuance.
146147
147148
### Service principal sign-ins
148149

articles/active-directory/reports-monitoring/reports-faq.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ metadata:
99
ms.workload: identity
1010
ms.topic: faq
1111
ms.subservice: report-monitor
12-
ms.date: 02/22/2023
12+
ms.date: 03/28/2023
1313
ms.author: sarahlipsey
1414
ms.reviewer: besiler
1515
ms.collection: M365-identity-device-management
@@ -40,6 +40,10 @@ sections:
4040
I currently use the https://graph.windows.net/<tenant-name>/reports/ endpoint APIs to pull Azure AD security reports (specific types of detections, such as leaked credentials or sign-ins from anonymous IP addresses) into our reporting systems programmatically. What should I switch to?
4141
answer: |
4242
You can use the [Identity Protection risk detections API](../identity-protection/howto-identity-protection-graph-api.md) to access security detections through Microsoft Graph. This new format gives greater flexibility in how you can query data. The format includes advanced filtering and field selection and standardizes risk detections into one type for easier integration into SIEMs and other data collection tools. Because the data is in a different format, you can't substitute a new query for your old queries. However, [the new API uses Microsoft Graph](/graph/api/resources/identityprotection-root), which is the Microsoft standard for such APIs as Microsoft 365 or Azure AD. So the work required can either extend your current Microsoft Graph investments or help you begin your transition to this new standard platform.
43+
- question: |
44+
I used the signInActivity resource to look up a user's last sign-in time, but it hasn't updated after a few hours. When will it be updated with the latest sign in time?
45+
answer: |
46+
The signInActivity resource is used to find inactive [users who haven't signed in for some time](howto-manage-inactive-user-accounts.md). It does not update in near real time; you should expect up to 24 hours before the property is updated for a given user. If you need to find the user's last sign-in activity more quickly than that, you can use the Azure AD sign-ins blade to see near real time sign-in activity for all your users.
4347
4448
- name: Activity logs
4549
questions:

0 commit comments

Comments
 (0)