Skip to content

Commit 28ffdbb

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 7aed9c4 + 83d1c5c commit 28ffdbb

File tree

206 files changed

+1403
-1364
lines changed

Some content is hidden

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

206 files changed

+1403
-1364
lines changed

.openpublishing.redirection.json

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20177,11 +20177,6 @@
2017720177
"redirect_url": "/azure/machine-learning/reference-azure-machine-learning-cli",
2017820178
"redirect_document_id": true
2017920179
},
20180-
{
20181-
"source_path_from_root": "/articles/machine-learning/service/reference-pipeline-yaml.md",
20182-
"redirect_url": "/azure/machine-learning/reference-pipeline-yaml",
20183-
"redirect_document_id": true
20184-
},
2018520180
{
2018620181
"source_path_from_root": "/articles/machine-learning/service/resource-known-issues.md",
2018720182
"redirect_url": "/azure/machine-learning/how-to-debug-visual-studio-code",
@@ -20757,6 +20752,12 @@
2075720752
"redirect_url": "/azure/machine-learning/tutorial-train-models-with-aml",
2075820753
"redirect_document_id": true
2075920754
},
20755+
{
20756+
"source_path_from_root": "/articles/machine-learning/service/reference-pipeline-yaml.md",
20757+
"redirect_url": "/azure/machine-learning/reference-yaml-job-pipeline",
20758+
"redirect_document_id": false
20759+
},
20760+
2076020761
{
2076120762
"source_path_from_root": "/articles/cognitive-services/QnAMaker/reference-precise-answering.md",
2076220763
"redirect_url": "/azure/cognitive-services/language/custom-question-answering/concepts/precise-answering",

articles/active-directory-b2c/partner-f5.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Tutorial to configure Azure Active Directory B2C with F5 BIG-IP
2+
title: Tutorial to extend Azure Active Directory B2C with F5 BIG-IP
33
titleSuffix: Azure AD B2C
44
description: Learn how to integrate Azure AD B2C authentication with F5 BIG-IP for secure hybrid access
55
author: gargi-sinha
@@ -12,7 +12,7 @@ ms.topic: how-to
1212
ms.date: 10/15/2021
1313
---
1414

15-
# Tutorial: Extend Azure Active Directory B2C to protect on-premises applications using F5 BIG-IP
15+
# Tutorial: Extend Azure Active Directory B2C using F5 BIG-IP
1616

1717
In this sample tutorial, learn how to integrate Azure Active Directory (Azure AD) B2C with [F5 BIG-IP Access Policy Manager (APM)](https://www.f5.com/services/resources/white-papers/easily-configure-secure-access-to-all-your-applications-via-azure-active-directory). This tutorial demonstrates how legacy applications can be securely exposed to the internet through BIG-IP security combined with Azure AD B2C pre-authentication, Conditional Access (CA), and Single sign-on (SSO).
1818

articles/active-directory/manage-apps/f5-aad-password-less-vpn.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Secure hybrid access with F5 VPN
2+
title: Configure F5 BIG-IP SSL-VPN solution in Azure AD
33
titleSuffix: Azure AD
4-
description: Tutorial for Azure Active Directory Single Sign-on (SSO) integration with F5 BIG-IP for Password-less VPN
4+
description: Tutorial to configure F5’s BIG-IP based Secure socket layer Virtual private network (SSL-VPN) solution with Azure Active Directory (AD) for Secure Hybrid Access (SHA)
55
services: active-directory
66
author: davidmu1
77
manager: martinco
@@ -15,11 +15,11 @@ ms.collection: M365-identity-device-management
1515
ms.reviewer: miccohen
1616
---
1717

18-
# Integrate F5 BIG-IP for Password-less VPN with Azure Active Directory
18+
# Configure F5 BIG-IP SSL-VPN solution in Azure AD
1919

20-
In this tutorial, learn how to integrate F5’s BIG-IP based Secure socket layer Virtual private network (SSL-VPN) solution with Azure Active Directory (AD) for Secure Hybrid Access (SHA).
20+
In this tutorial, learn how to configure F5’s BIG-IP based Secure socket layer Virtual private network (SSL-VPN) solution with Azure Active Directory (AD) for Secure Hybrid Access (SHA).
2121

22-
Integrating a BIG-IP SSL-VPN with Azure AD provides [many key benefits](f5-aad-integration.md), including:
22+
Configuring a BIG-IP SSL-VPN with Azure AD provides [many key benefits](f5-aad-integration.md), including:
2323

2424
- Improved Zero trust governance through [Azure AD pre-authentication and authorization](../../app-service/overview-authentication-authorization.md)
2525

articles/active-directory/manage-apps/f5-big-ip-forms-advanced.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: F5 BIG-IP APM and Azure AD SSO to form-based authentication applications
3-
description: Learn how to integrate F5's BIG-IP Access Policy Manager and Azure Active Directory for secure hybrid access to form-based applications.
2+
title: Configure F5 BIG-IP’s Access Policy Manager for form-based SSO
3+
description: Learn how to configure F5's BIG-IP Access Policy Manager and Azure Active Directory for secure hybrid access to form-based applications.
44
author: gargi-sinha
55
ms.service: active-directory
66
ms.subservice: app-mgmt
@@ -11,11 +11,11 @@ ms.author: gasinh
1111
ms.collection: M365-identity-device-management
1212
---
1313

14-
# Integrate Azure AD with F5 BIG-IP for form-based authentication single sign-on
14+
# Configure F5 BIG-IP Access Policy Manager for form-based SSO
1515

16-
In this article, you'll learn how to integrate F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to form-based applications.
16+
In this article, you'll learn how to configure F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to form-based applications.
1717

18-
Integrating BIG-IP published applications with Azure AD provides many benefits, including:
18+
Configuring BIG-IP published applications with Azure AD provides many benefits, including:
1919

2020
- Improved Zero Trust governance through Azure AD pre-authentication and authorization
2121
- Full single sign-on (SSO) between Azure AD and BIG-IP published services

articles/active-directory/manage-apps/f5-big-ip-header-advanced.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Azure Active Directory SSO integration with F5 BIG-IP for header-based authentication
3-
description: Learn how to integrate F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory SSO for header-based authentication
2+
title: Configure F5 BIG-IP Access Policy Manager for header-based SSO
3+
description: Learn how to configure F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory SSO for header-based authentication
44
services: active-directory
55
author: gargi-sinha
66
manager: martinco
@@ -13,11 +13,11 @@ ms.author: gasinh
1313
ms.collection: M365-identity-device-management
1414
---
1515

16-
# Tutorial: Integrate Azure Active Directory Single sign-on with F5 BIG-IP for header-based authentication
16+
# Tutorial: Configure F5 BIG-IP’s Access Policy Manager for header-based SSO
1717

18-
In this tutorial, you'll learn how to integrate F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to header-based applications.
18+
In this tutorial, you'll learn how to configure F5's BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to header-based applications.
1919

20-
Integrating BIG-IP published applications with Azure AD provides many benefits, including:
20+
Configuring BIG-IP published applications with Azure AD provides many benefits, including:
2121

2222
- Improved Zero trust governance through Azure AD pre-authentication and authorization
2323

@@ -434,4 +434,4 @@ For more information refer to these articles:
434434
- [What is Conditional Access?](../conditional-access/overview.md)
435435

436436
- [Microsoft Zero Trust framework to enable remote
437-
work](https://www.microsoft.com/security/blog/2020/04/02/announcing-microsoft-zero-trust-assessment-tool/)
437+
work](https://www.microsoft.com/security/blog/2020/04/02/announcing-microsoft-zero-trust-assessment-tool/)

articles/active-directory/manage-apps/f5-big-ip-ldap-header-easybutton.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: F5 BIG-IP Easy Button for Header and LDAP Single Sign-on
3-
description: Learn to integrate F5’s BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to header-based applications that also require session augmentation through Lightweight Directory Access Protocol (LDAP) sourced attributes.
2+
title: Configure F5 BIG-IP’s Easy Button for Header-based and LDAP SSO
3+
description: Learn to configure F5’s BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to header-based applications that also require session augmentation through Lightweight Directory Access Protocol (LDAP) sourced attributes.
44
services: active-directory
55
author: NishthaBabith-V
66
manager: martinco
@@ -13,11 +13,11 @@ ms.author: v-nisba
1313
ms.collection: M365-identity-device-management
1414
---
1515

16-
# Tutorial: F5 BIG-IP Easy Button for Header and LDAP Single Sign-on
16+
# Tutorial: Configure F5 BIG-IP’s Easy Button for Header-based and LDAP SSO
1717

18-
In this tutorial, you’ll learn to integrate F5’s BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to header-based applications that also require session augmentation through Lightweight Directory Access Protocol (LDAP) sourced attributes.
18+
In this tutorial, you’ll learn to configure F5’s BIG-IP Access Policy Manager (APM) and Azure Active Directory (Azure AD) for secure hybrid access to header-based applications that also require session augmentation through Lightweight Directory Access Protocol (LDAP) sourced attributes.
1919

20-
Integrating BIG-IP published applications with Azure AD provides many benefits, including:
20+
Configuring BIG-IP published applications with Azure AD provides many benefits, including:
2121

2222
* Improved zero-trust governance through Azure AD pre-authentication and authorization
2323

articles/active-directory/manage-apps/f5-bigip-deployment-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: devx-track-azurepowershell
1616
ms.reviewer: miccohen
1717
---
1818

19-
# Deploy an F5 BIG-IP Virtual Edition VM to Azure
19+
# Deploy F5 BIG-IP Virtual Edition VM in Azure
2020

2121
This tutorial walks you through the end to end process of deploying BIG-IP Vitural Edition (VE) in Azure IaaS. By the end of this tutorial you should have:
2222

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

Lines changed: 2 additions & 2 deletions
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 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 elses tenant, with all personal information removed. For more information, see [Admin experience](#admin-experience).
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**.
@@ -138,7 +138,7 @@ For Outlook on Windows, customers may choose to implement restrictions preventin
138138

139139
### Azure RMS and Office Message Encryption incompatibility
140140

141-
The [Azure Rights Management Service](https://docs.microsoft.com/azure/information-protection/what-is-azure-rms) (RMS) and [Office Message Encryption](https://docs.microsoft.com/microsoft-365/compliance/ome) features are not compatible with tenant restrictions. These features rely on signing your users into other tenants in order to get decryption keys for the encrypted documents. Because tenant restrictions blocks access to other tenants, encrypted mail and documents sent to your users from untrusted tenants will not be accessible.
141+
The [Azure Rights Management Service](/azure/information-protection/what-is-azure-rms) (RMS) and [Office Message Encryption](/microsoft-365/compliance/ome) features are not compatible with tenant restrictions. These features rely on signing your users into other tenants in order to get decryption keys for the encrypted documents. Because tenant restrictions blocks access to other tenants, encrypted mail and documents sent to your users from untrusted tenants will not be accessible.
142142

143143
## Testing
144144

articles/active-directory/manage-apps/toc.yml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -158,19 +158,19 @@
158158
href: datawiza-with-azure-ad.md
159159
- name: F5
160160
items:
161-
- name: F5 BIG-IP and Azure AD integration
161+
- name: Integrate F5 BIG-IP with Azure Active Directory
162162
href: f5-aad-integration.md
163-
- name: F5 BIG-IP VE deployment in Azure IaaS
163+
- name: Deploy F5 BIG-IP Virtual Edition VM in Azure
164164
href: f5-bigip-deployment-guide.md
165-
- name: F5 BIG-IP with Azure AD for passwordless VPN
165+
- name: Configure F5 BIG-IP SSL-VPN solution in Azure AD
166166
href: f5-aad-password-less-vpn.md
167-
- name: F5 BIG-IP with Azure AD for forms-based authentication SSO
167+
- name: Configure F5 BIG-IP Access Policy Manager for form-based SSO
168168
href: f5-big-ip-forms-advanced.md
169-
- name: F5 BIG-IP with Azure AD SSO for header based authentication
169+
- name: Configure F5 BIG-IP Access Policy Manager for header-based SSO
170170
href: f5-big-ip-header-advanced.md
171-
- name: Protect on-premises applications with F5 BIG-IP and Azure AD B2C
171+
- name: Extend Azure Active Directory B2C using F5 BIG-IP
172172
href: https://docs.microsoft.com/azure/active-directory-b2c/partner-f5
173-
- name: F5 BIG-IP for SSO to header-based and LDAP applications
173+
- name: Configure F5 BIG-IP Easy Button for Header-based and LDAP SSO
174174
href: f5-big-ip-ldap-header-easybutton.md
175175
- name: Silverfort
176176
href: silverfort-azure-ad-integration.md

articles/analysis-services/analysis-services-server-alias.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to create Azure Analysis Services server name aliases. Us
44
author: minewiskan
55
ms.service: azure-analysis-services
66
ms.topic: conceptual
7-
ms.date: 12/01/2020
7+
ms.date: 12/07/2021
88
ms.author: owend
99
ms.reviewer: minewiskan
1010
---
@@ -28,10 +28,16 @@ When connecting from a client, the alias server name is entered using **link://*
2828

2929
![Power BI Desktop connection](media/analysis-services-alias/aas-alias-connect-pbid.png)
3030

31+
> [!NOTE]
32+
> The link is evaluated on the client.
33+
3134
## Create an alias
3235

3336
To create an alias endpoint, you can use any method that returns a valid Azure Analysis Services server name. For example, a reference to a file in Azure Blob Storage containing the real server name, or create and publish an ASP.NET Web Forms application.
3437

38+
> [!IMPORTANT]
39+
> The location of the link file cannot require authentication.
40+
3541
In this example, an ASP.NET Web Forms Application is created in Visual Studio. The page reference and user control are removed from the Default.aspx page. The contents of Default.aspx are simply the following Page directive:
3642

3743
```

0 commit comments

Comments
 (0)