Skip to content

Commit f67c4e9

Browse files
committed
Merge branch 'release-azuresql' of https://github.com/MicrosoftDocs/azure-docs-pr into 05-21-mi-ml-in-new-scheme
2 parents ad2a907 + 439e1db commit f67c4e9

File tree

291 files changed

+5399
-3804
lines changed

Some content is hidden

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

291 files changed

+5399
-3804
lines changed

.openpublishing.publish.config.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -515,6 +515,11 @@
515515
"url": "https://github.com/Azure-Samples/azure-cosmos-java-getting-started",
516516
"branch": "master"
517517
},
518+
{
519+
"path_to_root": "azure-cosmos-java-sql-api-samples",
520+
"url": "https://github.com/Azure-Samples/azure-cosmos-java-sql-api-samples",
521+
"branch": "master"
522+
},
518523
{
519524
"path_to_root": "azure-storage-snippets",
520525
"url": "https://github.com/azure-samples/AzureStorageSnippets",

.openpublishing.redirection.json

Lines changed: 25 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39856,6 +39856,11 @@
3985639856
"redirect_url": "/azure/dev-spaces/",
3985739857
"redirect_document_id": false
3985839858
},
39859+
{
39860+
"source_path": "articles/dev-spaces/how-to/helm-3.md",
39861+
"redirect_url": "/azure/dev-spaces/",
39862+
"redirect_document_id": false
39863+
},
3985939864
{
3986039865
"source_path": "articles/monitoring/monitoring-overview.md",
3986139866
"redirect_url": "/azure/azure-monitor/overview",
@@ -48505,6 +48510,11 @@
4850548510
"redirect_url": "/azure/cognitive-services/form-recognizer/quickstarts/python-receipts",
4850648511
"redirect_document_id": false
4850748512
},
48513+
{
48514+
"source_path": "articles/cognitive-services/form-recognizer/quickstarts/dotnet-sdk.md",
48515+
"redirect_url": "/azure/cognitive-services/form-recognizer/quickstarts/client-library?pivots=programming-language-csharp",
48516+
"redirect_document_id": false
48517+
},
4850848518
{
4850948519
"source_path": "articles/cognitive-services/Content-Moderator/Review-Tool-User-Guide/Upload-Images.md",
4851048520
"redirect_url": "/azure/cognitive-services/content-moderator",
@@ -52494,6 +52504,16 @@
5249452504
"redirect_url": "/azure/batch/error-handling",
5249552505
"redirect_document_id": false
5249652506
},
52507+
{
52508+
"source_path": "articles/batch/batch-api-differences.md",
52509+
"redirect_url": "/azure/batch/batch-apis-tools",
52510+
"redirect_document_id": false
52511+
},
52512+
{
52513+
"source_path": "articles/batch/batch-integration-policies.md",
52514+
"redirect_url": "/azure/batch/policy-samples",
52515+
"redirect_document_id": false
52516+
},
5249752517
{
5249852518
"source_path": "articles/virtual-machines/troubleshooting/troubleshoot-vm-unresponsive-group-policy-local-users.md",
5249952519
"redirect_url": "/azure/virtual-machines/troubleshooting/unresponsive-vm-apply-group-policy",
@@ -53366,8 +53386,8 @@
5336653386
},
5336753387
{
5336853388
"source_path": "articles/sql-database/sql-database-glossary-terms.md",
53369-
"redirect_url": "/azure/azure-sql/glossary-terms",
53370-
"redirect_document_id": true
53389+
"redirect_url": "/azure/azure-sql/azure-sql-iaas-vs-paas-what-is-overview",
53390+
"redirect_document_id": false
5337153391
},
5337253392
{
5337353393
"source_path": "articles/sql-database/sql-database-high-availability.md",
@@ -54318,6 +54338,8 @@
5431854338
"source_path": "articles/data-factory/connector-azure-sql-database-managed-instance.md",
5431954339
"redirect_url": "/azure/data-factory/connector-azure-sql-managed-instance",
5432054340
"redirect_document_id": true
54321-
}
54341+
},
54342+
54343+
5432254344
]
5432354345
}

articles/active-directory-b2c/configure-tokens.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ You can configure the token lifetime on any user flow.
5050

5151
## Next steps
5252

53-
Learn more about how to [use access tokens](access-tokens.md).
53+
Learn more about how to [request access tokens](access-tokens.md).
5454

5555

5656

articles/active-directory/authentication/howto-mfa-nps-extension.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,9 +202,12 @@ If your previous computer certificate has expired, and a new certificate has bee
202202
203203
### Microsoft Azure Government additional steps
204204

205-
For customers that use Azure Government cloud, the following additional configuration steps are required on each NPS server:
205+
For customers that use Azure Government cloud, the following additional configuration steps are required on each NPS server.
206206

207-
1. Open **Registry Editor** on the NPS server.
207+
> [!IMPORTANT]
208+
> Only configure these registry settings if you're an Azure Government customer.
209+
210+
1. If you're an Azure Government customer, open **Registry Editor** on the NPS server.
208211
1. Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureMfa`. Set the following key values:
209212

210213
| Registry key | Value |

articles/active-directory/authentication/howto-sspr-deployment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ Note: For users who have [Password hash synchronization (PHS)](https://docs.micr
106106

107107
You can help users register quickly by deploying SSPR alongside another popular application or service in the organization. This action will generate a large volume of sign-ins and will drive registration.
108108

109-
Before deploying SSPR, you may opt to determine the number and the average cost of each password reset call. YOU can use this data post deployment to show the value SSPR is bringing to the organization.
109+
Before deploying SSPR, you may opt to determine the number and the average cost of each password reset call. You can use this data post deployment to show the value SSPR is bringing to the organization.
110110

111111
#### Enable combined registration for SSPR and MFA
112112

@@ -344,4 +344,4 @@ Audit logs for registration and password reset are available for 30 days. If sec
344344

345345
* [Consider implementing Azure AD password protection](https://docs.microsoft.com/azure/active-directory/authentication/concept-password-ban-bad)
346346

347-
* [Consider implementing Azure AD Smart Lockout](https://docs.microsoft.com/azure/active-directory/authentication/howto-password-smart-lockout)
347+
* [Consider implementing Azure AD Smart Lockout](https://docs.microsoft.com/azure/active-directory/authentication/howto-password-smart-lockout)

articles/active-directory/b2b/facebook-federation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
23
title: Add Facebook as an identity provider - Azure AD
34
description: Federate with Facebook to enable external users (guests) to sign in to your Azure AD apps with their own Facebook accounts.
45

articles/active-directory/cloud-provisioning/how-to-prerequisites.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -59,14 +59,9 @@ Run the [IdFix tool](https://docs.microsoft.com/office365/enterprise/prepare-dir
5959
- Your agents need access to login.windows.net and login.microsoftonline.com for initial registration. Open your firewall for those URLs as well.
6060
- For certificate validation, unblock the following URLs: mscrl.microsoft.com:80, crl.microsoft.com:80, ocsp.msocsp.com:80, and www\.microsoft.com:80. These URLs are used for certificate validation with other Microsoft products, so you might already have these URLs unblocked.
6161

62-
### Verify the port
63-
To verify that Azure is listening on port 443 and that your agent can communicate with it, use the following URL:
64-
65-
https://aadap-portcheck.connectorporttest.msappproxy.net/
66-
67-
This test verifies that your agents can communicate with Azure over port 443. Open a browser, and go to the previous URL from the server where the agent is installed.
62+
>[!NOTE]
63+
> Installing the cloud provisioning agent on Windows Server Core is not supported.
6864
69-
![Verification of port reachability](media/how-to-install/verify2.png)
7065

7166
### Additional requirements
7267
- [Microsoft .NET Framework 4.7.1](https://www.microsoft.com/download/details.aspx?id=56116)

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

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,19 @@ You can also investigate the sign-ins of a specific user by searching for sign-i
9696

9797
## Troubleshooting
9898

99+
### Why are queries failing due to a permissions error?
100+
101+
In order to access the workbook, you need the proper Azure AD permissions as well as Log Analytics workspace permissions. To test whether you have the proper workspace permissions by running a sample log analytics query:
102+
103+
1. Sign in to the **Azure portal**.
104+
1. Browse to **Azure Active Directory** > **Logs**.
105+
1. Type `SigninLogs` into the query box and select **Run**.
106+
1. If the query does not return any results, your workspace may not have been configured correctly.
107+
108+
![Troubleshoot failing queries](./media/howto-conditional-access-insights-reporting/query-troubleshoot-sign-in-logs.png)
109+
110+
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).
111+
99112
### Why is the workbook taking a long time to load?
100113

101114
Depending on the time range selected and the size of your tenant, the workbook may be evaluating an extraordinarily large number of sign-in events. For large tenants, the volume of sign-ins may exceed the query capacity of Log Analytics. Try shortening the time range to 4 hours to see if the workbook loads.

articles/active-directory/conditional-access/howto-conditional-access-policy-all-users-mfa.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The following steps will help create a Conditional Access policy to require All
5050
1. Select **Done**.
5151
1. Under **Cloud apps or actions** > **Include**, select **All cloud apps**.
5252
1. Under **Exclude**, select any applications that do not require multi-factor authentication.
53-
1. Under **Conditions** > **Client apps (Preview)**, set **Configure** to **Yes**, and select **Done**.
53+
1. Under **Conditions** > **Client apps (Preview)**, set **Configure** to **Yes**. Under **Select the client apps this policy will apply to** leave all defaults selected and select **Done**.
5454
1. Under **Access controls** > **Grant**, select **Grant access**, **Require multi-factor authentication**, and select **Select**.
5555
1. Confirm your settings and set **Enable policy** to **On**.
5656
1. Select **Create** to create to enable your policy.
Loading

0 commit comments

Comments
 (0)