Skip to content

Commit 0b5bfbd

Browse files
authored
Merge branch 'MicrosoftDocs:main' into cdcupdate
2 parents 01420c2 + 47428b6 commit 0b5bfbd

File tree

451 files changed

+6563
-3847
lines changed

Some content is hidden

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

451 files changed

+6563
-3847
lines changed

.openpublishing.publish.config.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -878,6 +878,12 @@
878878
"branch": "docs-snippets",
879879
"branch_mapping": {}
880880
},
881+
{
882+
"path_to_root": "ms-identity-python-webapp",
883+
"url": "https://github.com/Azure-Samples/ms-identity-python-webapp",
884+
"branch": "main",
885+
"branch_mapping": {}
886+
},
881887
{
882888
"path_to_root": "ms-identity-node",
883889
"url": "https://github.com/Azure-Samples/ms-identity-node",

.openpublishing.redirection.azure-monitor.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,16 @@
4545
"redirect_url": "/azure/azure-monitor/app/app-insights-overview",
4646
"redirect_document_id": false
4747
},
48+
{
49+
"source_path_from_root": "/articles/azure-monitor/app/correlation.md",
50+
"redirect_url": "/previous-versions/azure/azure-monitor/app/distributed-tracing-telemetry-correlation",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path_from_root": "/articles/azure-monitor/app/distributed-tracing.md",
55+
"redirect_url": "/previous-versions/azure/azure-monitor/app/distributed-tracing-telemetry-correlation",
56+
"redirect_document_id": false
57+
},
4858
{
4959
"source_path_from_root": "/articles/azure-monitor/app/console.md",
5060
"redirect_url": "/previous-versions/azure/azure-monitor/app/console",

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7548,6 +7548,11 @@
75487548
"redirect_url": "/azure/reliability/reliability-functions",
75497549
"redirect_document_id": false
75507550
},
7551+
{
7552+
"source_path_from_root": "/articles/azure-functions/functions-bindings-triggers-python.md",
7553+
"redirect_url": "/azure/azure-functions/functions-reference-python?pivots=python-mode-decorators#triggers-and-inputs",
7554+
"redirect_document_id": false
7555+
},
75517556
{
75527557
"source_path_from_root": "/articles/azure-government/documentation-government-k8.md",
75537558
"redirect_url": "/azure/azure-government",

articles/active-directory-domain-services/join-ubuntu-linux-vm.md

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Once the VM is deployed, follow the steps to connect to the VM using SSH.
5555

5656
To make sure that the VM host name is correctly configured for the managed domain, edit the */etc/hosts* file and set the hostname:
5757

58-
```console
58+
```bash
5959
sudo vi /etc/hosts
6060
```
6161

@@ -66,7 +66,7 @@ In the *hosts* file, update the *localhost* address. In the following example:
6666

6767
Update these names with your own values:
6868

69-
```console
69+
```config
7070
127.0.0.1 ubuntu.aaddscontoso.com ubuntu
7171
```
7272

@@ -78,7 +78,7 @@ The VM needs some additional packages to join the VM to the managed domain. To i
7878

7979
During the Kerberos installation, the *krb5-user* package prompts for the realm name in ALL UPPERCASE. For example, if the name of your managed domain is *aaddscontoso.com*, enter *AADDSCONTOSO.COM* as the realm. The installation writes the `[realm]` and `[domain_realm]` sections in */etc/krb5.conf* configuration file. Make sure that you specify the realm an ALL UPPERCASE:
8080

81-
```console
81+
```bash
8282
sudo apt-get update
8383
sudo apt-get install krb5-user samba sssd sssd-tools libnss-sss libpam-sss ntp ntpdate realmd adcli
8484
```
@@ -89,13 +89,13 @@ For domain communication to work correctly, the date and time of your Ubuntu VM
8989

9090
1. Open the *ntp.conf* file with an editor:
9191

92-
```console
92+
```bash
9393
sudo vi /etc/ntp.conf
9494
```
9595

9696
1. In the *ntp.conf* file, create a line to add your managed domain's DNS name. In the following example, an entry for *aaddscontoso.com* is added. Use your own DNS name:
9797
98-
```console
98+
```config
9999
server aaddscontoso.com
100100
```
101101
@@ -109,7 +109,7 @@ For domain communication to work correctly, the date and time of your Ubuntu VM
109109
110110
Run the following commands to complete these steps. Use your own DNS name with the `ntpdate` command:
111111
112-
```console
112+
```bash
113113
sudo systemctl stop ntp
114114
sudo ntpdate aaddscontoso.com
115115
sudo systemctl start ntp
@@ -121,7 +121,7 @@ Now that the required packages are installed on the VM and NTP is configured, jo
121121
122122
1. Use the `realm discover` command to discover the managed domain. The following example discovers the realm *AADDSCONTOSO.COM*. Specify your own managed domain name in ALL UPPERCASE:
123123
124-
```console
124+
```bash
125125
sudo realm discover AADDSCONTOSO.COM
126126
```
127127
@@ -135,13 +135,13 @@ Now that the required packages are installed on the VM and NTP is configured, jo
135135
136136
Again, the managed domain name must be entered in ALL UPPERCASE. In the following example, the account named `[email protected]` is used to initialize Kerberos. Enter your own user account that's a part of the managed domain:
137137

138-
```console
139-
138+
```bash
139+
sudo kinit -V [email protected]
140140
```
141141

142142
1. Finally, join the VM to the managed domain using the `realm join` command. Use the same user account that's a part of the managed domain that you specified in the previous `kinit` command, such as `[email protected]`:
143143
144-
```console
144+
```bash
145145
sudo realm join --verbose AADDSCONTOSO.COM -U '[email protected]' --install=/
146146
```
147147
@@ -155,7 +155,7 @@ If your VM can't successfully complete the domain-join process, make sure that t
155155
156156
If you received the error *Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database)*, open the file */etc/krb5.conf* and add the following code in `[libdefaults]` section and try again:
157157
158-
```console
158+
```config
159159
rdns=false
160160
```
161161
@@ -165,21 +165,21 @@ One of the packages installed in a previous step was for System Security Service
165165
166166
1. Open the *sssd.conf* file with an editor:
167167
168-
```console
168+
```bash
169169
sudo vi /etc/sssd/sssd.conf
170170
```
171171
172172
1. Comment out the line for *use_fully_qualified_names* as follows:
173173
174-
```console
174+
```config
175175
# use_fully_qualified_names = True
176176
```
177177
178178
When done, save and exit the *sssd.conf* file using the `:wq` command of the editor.
179179
180180
1. To apply the change, restart the SSSD service:
181181
182-
```console
182+
```bash
183183
sudo systemctl restart sssd
184184
```
185185
@@ -193,37 +193,37 @@ By default, users can only sign in to a VM using SSH public key-based authentica
193193
194194
1. Open the *sshd_conf* file with an editor:
195195
196-
```console
196+
```bash
197197
sudo vi /etc/ssh/sshd_config
198198
```
199199
200200
1. Update the line for *PasswordAuthentication* to *yes*:
201201
202-
```console
202+
```config
203203
PasswordAuthentication yes
204204
```
205205
206206
When done, save and exit the *sshd_conf* file using the `:wq` command of the editor.
207207
208208
1. To apply the changes and let users sign in using a password, restart the SSH service:
209209
210-
```console
210+
```bash
211211
sudo systemctl restart ssh
212212
```
213213
214214
### Configure automatic home directory creation
215215
216216
To enable automatic creation of the home directory when a user first signs in, complete the following steps:
217217
218-
1. Open the */etc/pam.d/common-session* file in an editor:
218+
1. Open the `/etc/pam.d/common-session` file in an editor:
219219
220-
```console
220+
```bash
221221
sudo vi /etc/pam.d/common-session
222222
```
223223
224224
1. Add the following line in this file below the line `session optional pam_sss.so`:
225225
226-
```console
226+
```config
227227
session required pam_mkhomedir.so skel=/etc/skel/ umask=0077
228228
```
229229
@@ -235,13 +235,13 @@ To grant members of the *AAD DC Administrators* group administrative privileges
235235
236236
1. Open the *sudoers* file for editing:
237237
238-
```console
238+
```bash
239239
sudo visudo
240240
```
241241
242242
1. Add the following entry to the end of */etc/sudoers* file:
243243
244-
```console
244+
```config
245245
# Add 'AAD DC Administrators' group members as admins.
246246
%AAD\ DC\ Administrators ALL=(ALL) NOPASSWD:ALL
247247
```
@@ -254,29 +254,29 @@ To verify that the VM has been successfully joined to the managed domain, start
254254
255255
1. Create a new SSH connection from your console. Use a domain account that belongs to the managed domain using the `ssh -l` command, such as `[email protected]` and then enter the address of your VM, such as *ubuntu.aaddscontoso.com*. If you use the Azure Cloud Shell, use the public IP address of the VM rather than the internal DNS name.
256256
257-
```console
258-
ssh -l [email protected] ubuntu.aaddscontoso.com
257+
```bash
258+
sudo ssh -l [email protected] ubuntu.aaddscontoso.com
259259
```
260260
261261
1. When you've successfully connected to the VM, verify that the home directory was initialized correctly:
262262

263-
```console
264-
pwd
263+
```bash
264+
sudo pwd
265265
```
266266

267267
You should be in the */home* directory with your own directory that matches the user account.
268268

269269
1. Now check that the group memberships are being resolved correctly:
270270

271-
```console
272-
id
271+
```bash
272+
sudo id
273273
```
274274

275275
You should see your group memberships from the managed domain.
276276

277277
1. If you signed in to the VM as a member of the *AAD DC Administrators* group, check that you can correctly use the `sudo` command:
278278

279-
```console
279+
```bash
280280
sudo apt-get update
281281
```
282282

articles/active-directory/authentication/how-to-certificate-based-authentication.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,10 @@ To enable the certificate-based authentication and configure user bindings in th
7272
1. To delete a CA certificate, select the certificate and click **Delete**.
7373
1. Click **Columns** to add or delete columns.
7474

75-
### Configure certification authorities using PowerShell
75+
>[!NOTE]
76+
>Upload of new CAs will fail when any of the existing CAs are expired. Tenant Admin should delete the expired CAs and then upload the new CA.
77+
78+
### Configure certification authorities(CA) using PowerShell
7679

7780
Only one CRL Distribution Point (CDP) for a trusted CA is supported. The CDP can only be HTTP URLs. Online Certificate Status Protocol (OCSP) or Lightweight Directory Access Protocol (LDAP) URLs aren't supported.
7881

@@ -87,6 +90,9 @@ Only one CRL Distribution Point (CDP) for a trusted CA is supported. The CDP can
8790
[!INCLUDE [Get-AzureAD](../../../includes/active-directory-authentication-get-trusted-azuread.md)]
8891
### Add
8992

93+
>[!NOTE]
94+
>Upload of new CAs will fail when any of the existing CAs are expired. Tenant Admin should delete the expired CAs and then upload the new CA.
95+
9096
[!INCLUDE [New-AzureAD](../../../includes/active-directory-authentication-new-trusted-azuread.md)]
9197

9298
**AuthorityType**

articles/active-directory/conditional-access/concept-conditional-access-report-only.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 01/24/2023
9+
ms.date: 03/30/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -31,7 +31,7 @@ Report-only mode is a new Conditional Access policy state that allows administra
3131
> [!WARNING]
3232
> Policies in report-only mode that require compliant devices may prompt users on Mac, iOS, and Android to select a device certificate during policy evaluation, even though device compliance is not enforced. These prompts may repeat until the device is made compliant. To prevent end users from receiving prompts during sign-in, exclude device platforms Mac, iOS and Android from report-only policies that perform device compliance checks. Note that report-only mode is not applicable for Conditional Access policies with "User Actions" scope.
3333
34-
![Report-only tab in Azure AD sign-in log](./media/concept-conditional-access-report-only/report-only-detail-in-sign-in-log.png)
34+
![Screenshot showing the report-only tab in a sign-in log.](./media/concept-conditional-access-report-only/report-only-detail-in-sign-in-log.png)
3535

3636
## Policy results
3737

articles/active-directory/conditional-access/concept-conditional-access-session.md

Lines changed: 8 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: conditional-access
88
ms.topic: conceptual
9-
ms.date: 02/27/2023
9+
ms.date: 03/28/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -75,15 +75,20 @@ For more information, see the article [Configure authentication session manageme
7575

7676
- **Disable** only work when **All cloud apps** are selected, no conditions are selected, and **Disable** is selected under **Session** > **Customize continuous access evaluation** in a Conditional Access policy. You can choose to disable all users or specific users and groups.
7777

78-
7978
:::image type="content" source="media/concept-conditional-access-session/continuous-access-evaluation-session-controls.png" alt-text="CAE Settings in a new Conditional Access policy in the Azure portal." lightbox="media/concept-conditional-access-session/continuous-access-evaluation-session-controls.png":::
8079

81-
## Disable resilience defaults (Preview)
80+
## Disable resilience defaults
8281

8382
During an outage, Azure AD extends access to existing sessions while enforcing Conditional Access policies.
8483

8584
If resilience defaults are disabled, access is denied once existing sessions expire. For more information, see the article [Conditional Access: Resilience defaults](resilience-defaults.md).
8685

86+
## Require token protection for sign-in sessions (preview)
87+
88+
Token protection (sometimes referred to as token binding in the industry) attempts to reduce attacks using token theft by ensuring a token is usable only from the intended device. When an attacker is able to steal a token, by hijacking or replay, they can impersonate their victim until the token expires or is revoked. Token theft is thought to be a relatively rare event, but the damage from it can be significant.
89+
90+
The preview works for specific scenarios only. For more information, see the article [Conditional Access: Token protection (preview)](concept-token-protection.md).
91+
8792
## Next steps
8893

8994
- [Conditional Access common policies](concept-conditional-access-policy-common.md)

articles/active-directory/conditional-access/howto-conditional-access-insights-reporting.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 02/27/2023
9+
ms.date: 03/28/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -43,7 +43,7 @@ To access the insights and reporting workbook:
4343

4444
The insights and reporting dashboard lets you see the impact of one or more Conditional Access policies over a specified period. Start by setting each of the parameters at the top of the workbook.
4545

46-
![Conditional Access Insights and Reporting dashboard in the Azure portal](./media/howto-conditional-access-insights-reporting/conditional-access-insights-and-reporting-dashboard.png)
46+
:::image type="content" source="media/howto-conditional-access-insights-reporting/conditional-access-insights-and-reporting-dashboard.png" alt-text="Screenshot showing the Conditional Access insights and reporting workbook." lightbox="media/howto-conditional-access-insights-reporting/conditional-access-insights-and-reporting-dashboard-expanded.png":::
4747

4848
**Conditional Access policy**: Select one or more Conditional Access policies to view their combined impact. Policies are separated into two groups: Enabled and Report-only policies. By default, all Enabled policies are selected. These enabled policies are the policies currently enforced in your tenant.
4949

@@ -59,7 +59,7 @@ The insights and reporting dashboard lets you see the impact of one or more Cond
5959

6060
Once the parameters have been set, the impact summary loads. The summary shows how many users or sign-ins during the time range resulted in “Success”, “Failure”, ”User action required” or “Not applied” when the selected policies were evaluated.
6161

62-
![Impact summary in the Conditional Access workbook](./media/howto-conditional-access-insights-reporting/workbook-impact-summary.png)
62+
![Screenshot showing an example impact summary in the Conditional Access workbook.](./media/howto-conditional-access-insights-reporting/workbook-impact-summary.png)
6363

6464
**Total**: The number of users or sign-ins during the time period where at least one of the selected policies was evaluated.
6565

@@ -73,15 +73,15 @@ Once the parameters have been set, the impact summary loads. The summary shows h
7373

7474
### Understanding the impact
7575

76-
![Workbook breakdown per condition and status](./media/howto-conditional-access-insights-reporting/workbook-breakdown-condition-and-status.png)
76+
![Screenshot showing a workbook breakdown per condition and status.](./media/howto-conditional-access-insights-reporting/workbook-breakdown-condition-and-status.png)
7777

7878
View the breakdown of users or sign-ins for each of the conditions. You can filter the sign-ins of a particular result (for example, Success or Failure) by selecting on of the summary tiles at the top of the workbook. You can see the breakdown of sign-ins for each of the Conditional Access conditions: device state, device platform, client app, location, application, and sign-in risk.
7979

8080
## Sign-in details
8181

82-
![Workbook sign-in details](./media/howto-conditional-access-insights-reporting/workbook-sign-in-details.png)
82+
![Screenshot showing workbook sign-in details.](./media/howto-conditional-access-insights-reporting/workbook-sign-in-details.png)
8383

84-
You can also investigate the sign-ins of a specific user by searching for sign-ins at the bottom of the dashboard. The query on the left displays the most frequent users. Selecting a user filters the query to the right.
84+
You can also investigate the sign-ins of a specific user by searching for sign-ins at the bottom of the dashboard. The query displays the most frequent users. Selecting a user filters the query.
8585

8686
> [!NOTE]
8787
> When downloading the Sign-ins logs, choose JSON format to include Conditional Access report-only result data.
@@ -110,7 +110,7 @@ In order to access the workbook, you need the proper Azure AD permissions and Lo
110110
1. Type `SigninLogs` into the query box and select **Run**.
111111
1. If the query doesn't return any results, your workspace may not have been configured correctly.
112112

113-
![Troubleshoot failing queries](./media/howto-conditional-access-insights-reporting/query-troubleshoot-sign-in-logs.png)
113+
![Screenshot showing how to troubleshoot failing queries.](./media/howto-conditional-access-insights-reporting/query-troubleshoot-sign-in-logs.png)
114114

115115
For more information about how to stream Azure AD sign-in logs to a Log Analytics workspace, see the article [Integrate Azure AD logs with Azure Monitor logs](../reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md).
116116

Loading
Loading

0 commit comments

Comments
 (0)