Skip to content

Commit 22856f7

Browse files
authored
Merge pull request #178797 from MicrosoftDocs/master
11/04 PM Publish
2 parents 96deccc + 6d44da7 commit 22856f7

File tree

291 files changed

+2195
-868
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

+2195
-868
lines changed

.openpublishing.redirection.synapse-analytics.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,11 @@
6464
"source_path_from_root": "/articles/synapse-analytics/machine-learning/tutorial-spark-pool-filesystem-spec.md",
6565
"redirect_url": "/azure/synapse-analytics/spark/tutorial-spark-pool-filesystem-spec",
6666
"redirect_document_id": false
67+
},
68+
{
69+
"source_path_from_root": "/articles/synapse-analytics/security/synapse-workspace-managed-identity.md",
70+
"redirect_url": "/azure/data-factory/data-factory-service-identity",
71+
"redirect_document_id": false
6772
}
6873
]
6974
}

articles/active-directory/app-provisioning/whats-new-docs.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory application provisioning"
33
description: "New and updated documentation for the Azure Active Directory application provisioning."
4-
ms.date: 10/05/2021
4+
ms.date: 11/04/2021
55
ms.service: active-directory
66
ms.subservice: app-provisioning
77
ms.topic: reference
@@ -15,6 +15,13 @@ manager: karenh444
1515

1616
Welcome to what's new in Azure Active Directory application provisioning documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the provisioning service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
1717

18+
## October 2021
19+
20+
### New articles
21+
22+
- [Configuring Azure AD to provision users into LDAP directories](on-premises-ldap-connector-configure.md)
23+
24+
1825
## September 2021
1926

2027
### New articles

articles/active-directory/app-proxy/whats-new-docs.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory application proxy"
33
description: "New and updated documentation for the Azure Active Directory application proxy."
4-
ms.date: 10/05/2021
4+
ms.date: 11/04/2021
55
ms.service: active-directory
66
ms.subservice: app-proxy
77
ms.topic: reference
@@ -15,6 +15,14 @@ manager: karenh444
1515

1616
Welcome to what's new in Azure Active Directory application proxy documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
1717

18+
## October 2021
19+
20+
### Updated articles
21+
22+
- [Troubleshoot Application Proxy problems and error messages](application-proxy-troubleshoot.md)
23+
- [Active Directory (Azure AD) Application Proxy frequently asked questions](application-proxy-faq.yml)
24+
25+
1826
## September 2021
1927

2028
### Updated articles

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,9 @@ For more information, see the article [Configure authentication session manageme
7878
- Non-CAE capable clients shouldn't get a regular token for CAE-capable services.
7979
- Reject when IP seen by resource provider isn't in the allowed range.
8080

81+
> [!NOTE]
82+
> You should only enable strict enforcement after you ensure that all the client applications support CAE and you have included all your IP addresses seen by Azure AD and the resource providers, like Exchange online and Azure Resource Mananger, in your location policy under Conditional Access. Otherwise, users in your tenants could be blocked.
83+
8184
:::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":::
8285

8386
## Disable resilience defaults (Preview)

articles/active-directory/manage-apps/tenant-restrictions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ The headers should include the following elements:
7373

7474
- For *Restrict-Access-To-Tenants*, use a value of \<permitted tenant list\>, which is a comma-separated list of tenants you want to allow users to access. Any domain that is registered with a tenant can be used to identify the tenant in this list, as well as the directory ID itself. For an example of all three ways of describing a tenant, the name/value pair to allow Contoso, Fabrikam, and Microsoft looks like: `Restrict-Access-To-Tenants: contoso.com,fabrikam.onmicrosoft.com,72f988bf-86f1-41af-91ab-2d7cd011db47`
7575

76-
- For *Restrict-Access-Context*, use a value of a single directory ID, declaring which tenant is setting the tenant restrictions. For example, to declare Contoso as the tenant that set the tenant restrictions policy, the name/value pair looks like: `Restrict-Access-Context: 456ff232-35l2-5h23-b3b3-3236w0826f3d`. You **must** use your own directory ID in this spot in order to get logs for these authentications.
76+
- For *Restrict-Access-Context*, use a value of a single directory ID, declaring which tenant is setting the tenant restrictions. For example, to declare Contoso as the tenant that set the tenant restrictions policy, the name/value pair looks like: `Restrict-Access-Context: 456ff232-35l2-5h23-b3b3-3236w0826f3d`. You *must* use your own directory ID here to get logs for these authentications. If you use any directory ID other than your own, those sign-in logs *will* appear in someone else’s tenant, with all personal information removed. For more information, see [Admin experience](#admin-experience).
7777

7878
> [!TIP]
7979
> You can find your directory ID in the [Azure Active Directory portal](https://aad.portal.azure.com/). Sign in as an administrator, select **Azure Active Directory**, then select **Properties**.

articles/active-directory/manage-apps/whats-new-docs.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory application management"
33
description: "New and updated documentation for the Azure Active Directory application management."
4-
ms.date: 10/05/2021
4+
ms.date: 11/04/2021
55
ms.service: active-directory
66
ms.subservice: app-mgmt
77
ms.topic: reference
@@ -16,6 +16,23 @@ reviewer: napuri
1616

1717
Welcome to what's new in Azure Active Directory application management documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the application management service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
1818

19+
## October 2021
20+
21+
### Updated articles
22+
23+
- [Manage consent to applications and evaluate consent requests in Azure Active Directory](manage-consent-requests.md)
24+
- [What is application management in Azure Active Directory?](what-is-application-management.md)
25+
- [Configure how end-users consent to applications using Azure Active Directory](configure-user-consent.md)
26+
- [What is single sign-on in Azure Active Directory?](what-is-single-sign-on.md)
27+
- [Assign enterprise application owners](assign-app-owners.md)
28+
- [Configure the admin consent workflow](configure-admin-consent-workflow.md)
29+
- [Secure hybrid access: Secure legacy apps with Azure Active Directory](secure-hybrid-access.md)
30+
- [Azure Active Directory application management: What's new](whats-new-docs.md)
31+
- [Tutorial: Migrate Okta sign on policies to Azure Active Directory Conditional Access](migrate-okta-sign-on-policies-to-azure-active-directory-conditional-access.md)
32+
- [Tutorial: Migrate Okta sync provisioning to Azure AD Connect-based synchronization](migrate-okta-sync-provisioning-to-azure-active-directory.md)
33+
- [Manage certificates for federated single sign-on in Azure Active Directory](manage-certificates-for-federated-single-sign-on.md)
34+
35+
1936
## September 2021
2037

2138
### New articles

articles/active-directory/roles/security-planning.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ description: Ensure that your organization's administrative access and administr
55
services: active-directory
66
keywords:
77
author: rolyon
8-
manager: daveba
8+
manager: KarenH444
99
ms.author: rolyon
10-
ms.date: 11/05/2020
10+
ms.date: 11/04/2021
1111
ms.topic: conceptual
1212
ms.service: active-directory
1313
ms.workload: identity
@@ -174,7 +174,7 @@ Azure AD Identity Protection is an algorithm-based monitoring and reporting tool
174174

175175
#### Obtain your Microsoft 365 Secure Score (if using Microsoft 365)
176176

177-
Secure Score looks at your settings and activities for the Microsoft 365 services you're using and compares them to a baseline established by Microsoft. You'll get a score based on how aligned you are with security practices. Anyone who has the administrator permissions for a Microsoft 365 Business Standard or Enterprise subscription can access the Secure Score at `https://securescore.office.com`.
177+
Secure Score looks at your settings and activities for the Microsoft 365 services you're using and compares them to a baseline established by Microsoft. You'll get a score based on how aligned you are with security practices. Anyone who has the administrator permissions for a Microsoft 365 Business Standard or Enterprise subscription can access the Secure Score at `https://security.microsoft.com/securescore`.
178178

179179
#### Review the Microsoft 365 security and compliance guidance (if using Microsoft 365)
180180

articles/aks/TOC.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,8 @@
186186
href: availability-zones.md
187187
- name: Use node pools
188188
items:
189+
- name: Node pool snapshot
190+
href: node-pool-snapshot.md
189191
- name: Use multiple node pools
190192
href: use-multiple-node-pools.md
191193
- name: Use spot node pools
@@ -320,9 +322,9 @@
320322
href: azure-disk-customer-managed-keys.md
321323
- name: Enable host-based encryption
322324
href: enable-host-encryption.md
323-
- name: Secrets Store CSI driver
325+
- name: Secrets Store CSI Driver
324326
items:
325-
- name: Secrets Store CSI driver configuration
327+
- name: Secrets Store CSI Driver configuration
326328
href: csi-secrets-store-driver.md
327329
- name: Provide Azure Key Vault access
328330
href: csi-secrets-store-identity-access.md

articles/aks/csi-secrets-store-driver.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@ When creating a SecretProviderClass, use the `secretObjects` field to define the
202202
> Make sure the `objectName` in `secretObjects` matches the file name of the mounted content. If `objectAlias` is used instead, then it should match the object alias.
203203

204204
```yml
205-
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
205+
apiVersion: secrets-store.csi.x-k8s.io/v1
206206
kind: SecretProviderClass
207207
metadata:
208208
name: azure-sync

articles/aks/csi-secrets-store-nginx-tls.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Select a [method to provide an access identity][csi-ss-identity-access] and conf
6767
See the following for an example of what your SecretProviderClass might look like:
6868

6969
```yml
70-
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
70+
apiVersion: secrets-store.csi.x-k8s.io/v1
7171
kind: SecretProviderClass
7272
metadata:
7373
name: azure-tls

0 commit comments

Comments
 (0)