Skip to content

Commit 15e6ac0

Browse files
author
dksimpson
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into DKS-US1712683-bing-entity-search
2 parents ebacba9 + 83bf60b commit 15e6ac0

File tree

290 files changed

+5069
-3320
lines changed

Some content is hidden

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

290 files changed

+5069
-3320
lines changed

.openpublishing.redirection.json

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20295,6 +20295,36 @@
2029520295
"redirect_url": "/azure/marketplace/marketplace-commercial-transaction-capabilities-and-considerations",
2029620296
"redirect_document_id": false
2029720297
},
20298+
{
20299+
"source_path": "articles/marketplace/cloud-partner-portal/consulting-services/cloud-partner-portal-consulting-services-publishing-offer.md",
20300+
"redirect_url": "/azure/marketplace/partner-center-portal/create-consulting-service-offer",
20301+
"redirect_document_id": false
20302+
},
20303+
{
20304+
"source_path": "articles/marketplace/cloud-partner-portal/consulting-services/cpp-consulting-service-prerequisites.md",
20305+
"redirect_url": "/azure/marketplace/partner-center-portal/consulting-service-prerequisites",
20306+
"redirect_document_id": false
20307+
},
20308+
{
20309+
"source_path": "articles/marketplace/cloud-partner-portal/consulting-services/cpp-consulting-service-create-offer.md",
20310+
"redirect_url": "/azure/marketplace/partner-center-portal/create-consulting-service-offer",
20311+
"redirect_document_id": false
20312+
},
20313+
{
20314+
"source_path": "articles/marketplace/cloud-partner-portal/consulting-services/cpp-consulting-service-define-offer-settings.md",
20315+
"redirect_url": "/azure/marketplace/partner-center-portal/create-consulting-service-offer",
20316+
"redirect_document_id": false
20317+
},
20318+
{
20319+
"source_path": "articles/marketplace/cloud-partner-portal/consulting-services/cpp-consulting-service-storefront-details.md",
20320+
"redirect_url": "/azure/marketplace/partner-center-portal/create-consulting-service-offer",
20321+
"redirect_document_id": false
20322+
},
20323+
{
20324+
"source_path": "articles/marketplace/cloud-partner-portal/consulting-services/cpp-consulting-service-publish-offer.md",
20325+
"redirect_url": "/azure/marketplace/partner-center-portal/create-consulting-service-offer",
20326+
"redirect_document_id": false
20327+
},
2029820328
{
2029920329
"source_path": "articles/multi-factor-authentication/multi-factor-authentication-app-faq.md",
2030020330
"redirect_url": "./end-user/microsoft-authenticator-app-faq",
4 KB
Loading

articles/active-directory/develop/reference-v2-libraries.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,7 @@ See also [Scenarios by supported platforms and languages](authentication-flows-a
8484
| Platform | Library name | Tested version | Source code | Sample |
8585
|:---:|:---:|:---:|:---:|:---:|
8686
|![JavaScript](media/sample-v2-code/logo_js.png)|[Hello.js](https://adodson.com/hello.js/) | Version 1.13.5 |[Hello.js](https://github.com/MrSwitch/hello.js) |[SPA](https://github.com/Azure-Samples/active-directory-javascript-graphapi-v2) |
87+
|![Vue](media/sample-v2-code/logo_vue.png)|[Vue MSAL](https://github.com/mvertopoulos/vue-msal) | Version 3.0.3 |[vue-msal](https://github.com/mvertopoulos/vue-msal) | |
8788
| ![Java](media/sample-v2-code/logo_java.png) | [Scribe Java](https://github.com/scribejava/scribejava) | [Version 3.2.0](https://github.com/scribejava/scribejava/releases/tag/scribejava-3.2.0) | [ScribeJava](https://github.com/scribejava/scribejava/) | |
8889
| ![Java](media/sample-v2-code/logo_java.png) | [Gluu OpenID Connect library](https://github.com/GluuFederation/oxAuth) | [Version 3.0.2](https://github.com/GluuFederation/oxAuth/releases/tag/3.0.2) | [Gluu OpenID Connect library](https://github.com/GluuFederation/oxAuth) | |
8990
| ![Python](media/sample-v2-code/logo_python.png) | [Requests-OAuthlib](https://github.com/requests/requests-oauthlib) | [Version 1.2.0](https://github.com/requests/requests-oauthlib/releases/tag/v1.2.0) | [Requests-OAuthlib](https://github.com/requests/requests-oauthlib) | |

articles/active-directory/hybrid/reference-connect-version-history.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,17 @@ Not all releases of Azure AD Connect will be made available for auto upgrade. Th
4343
>
4444
>Please refer to [this article](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-upgrade-previous-version) to learn more about how to upgrade Azure AD Connect to the latest version.
4545
46+
## 1.5.30.0
47+
48+
### Release status
49+
05/07/2020: Released for download
50+
51+
### Fixed issues
52+
- Fixed an issue where unselected domains were getting incorrectly selected from the wizard UI.
53+
- Fixed an issue in the ADSyncConfig PowerShell module, where invoking DSACLS command used in all the Set-ADSync* Permissions cmdlets would cause one of the following errors:
54+
- `GrantAclsNoInheritance : The parameter is incorrect. The command failed to complete successfully.`
55+
- `GrantAcls : No GUID Found for computer …`
56+
4657
## 1.5.29.0
4758

4859
### Release status
@@ -100,6 +111,7 @@ This hotfix build fixes an issue with build 1.5.18.0 if you have the Group Filte
100111
- Fixed an issue with the creation of the Azure Active Directory synchronization account where enabling Directory Extensions or PHS may fail because the account has not propagated across all service replicas before attempted use.
101112
- Fixed a bug in the sync errors compression utility that was not handling surrogate characters correctly.
102113
- Fixed a bug in the auto upgrade which left the server in the scheduler suspended state.
114+
- Fixed a bug in the Domain/OU filtering page that would remove the Run Profiles of a domain by just partially expanding the domain tree, without making any changes.
103115

104116
## 1.4.38.0
105117
### Release status

articles/active-directory/saas-apps/smarteru-tutorial.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,11 @@ ms.date: 03/19/2019
1818
ms.author: jeedes
1919

2020
---
21+
# Tutorial: Azure Active Directory integration with SmarterU
2122

2223
> [!NOTE]
2324
> The process for integrating SmarterU with Azure Active Directory is also documented and maintained in the [SmarterU help system](https://help.smarteru.com/ID2053086).
2425
25-
# Tutorial: Azure Active Directory integration with SmarterU
26-
2726
In this tutorial, you learn how to integrate SmarterU with Azure Active Directory (Azure AD).
2827
Integrating SmarterU with Azure AD provides you with the following benefits:
2928

articles/active-directory/users-groups-roles/TOC.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@
6868
href: /azure/active-directory/b2b/use-dynamic-groups?context=azure/active-directory/users-groups-roles/context/ugr-context
6969
- name: Manage your directory
7070
items:
71-
- name: Administer your directory
71+
- name: Azure AD organizations
7272
href: /azure/active-directory/fundamentals/active-directory-administer?context=azure/active-directory/users-groups-roles/context/ugr-context
7373
- name: Manage domain names
7474
href: domains-manage.md
@@ -84,7 +84,7 @@
8484
href: /azure/active-directory/connect/active-directory-aadconnect?context=azure/active-directory/users-groups-roles/context/ugr-context
8585
- name: Manage groups
8686
items:
87-
- name: Manage access with Azure AD groups
87+
- name: Manage access with groups
8888
href: /azure/active-directory/fundamentals/active-directory-manage-groups?context=azure/active-directory/users-groups-roles/context/ugr-context
8989
- name: Create a group (Azure portal)
9090
href: /azure/active-directory/fundamentals/active-directory-groups-create-azure-portal?context=azure/active-directory/users-groups-roles/context/ugr-context
@@ -134,6 +134,8 @@
134134
href: groups-assign-sensitivity-labels.md
135135
- name: Assign licenses
136136
items:
137+
- name: Assign licenses to users
138+
href: /azure/active-directory/fundamentals/license-users-groups?context=azure/active-directory/users-groups-roles/context/ugr-context
137139
- name: Assign licenses to a group
138140
href: licensing-groups-assign.md
139141
- name: Resolve group license problems

articles/active-directory/users-groups-roles/my-staff-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: article
99
ms.service: active-directory
1010
ms.subservice: user-help
1111
ms.workload: identity
12-
ms.date: 05/01/2020
12+
ms.date: 05/08/2020
1313
ms.author: curtand
1414
ms.reviewer: sahenry
1515
ms.custom: oldportal;it-pro;

articles/aks/concepts-security.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Concepts - Security in Azure Kubernetes Services (AKS)
33
description: Learn about security in Azure Kubernetes Service (AKS), including master and node communication, network policies, and Kubernetes secrets.
44
services: container-service
55
ms.topic: conceptual
6-
ms.date: 03/01/2019
6+
ms.date: 05/08/2020
77

88
---
99

@@ -23,7 +23,9 @@ This article introduces the core concepts that secure your applications in AKS:
2323

2424
In AKS, the Kubernetes master components are part of the managed service provided by Microsoft. Each AKS cluster has its own single-tenanted, dedicated Kubernetes master to provide the API Server, Scheduler, etc. This master is managed and maintained by Microsoft.
2525

26-
By default, the Kubernetes API server uses a public IP address and a fully qualified domain name (FQDN). You can control access to the API server using Kubernetes role-based access controls and Azure Active Directory. For more information, see [Azure AD integration with AKS][aks-aad].
26+
By default, the Kubernetes API server uses a public IP address and a fully qualified domain name (FQDN). You can limit access to the API server endpoint using [authorized IP ranges][authorized-ip-ranges]. You can also create a fully [private cluster][private-clusters] to limit API server access to your virtual network.
27+
28+
You can control access to the API server using Kubernetes role-based access controls and Azure Active Directory. For more information, see [Azure AD integration with AKS][aks-aad].
2729

2830
## Node security
2931

@@ -62,6 +64,10 @@ For connectivity and security with on-premises networks, you can deploy your AKS
6264

6365
To filter the flow of traffic in virtual networks, Azure uses network security group rules. These rules define the source and destination IP ranges, ports, and protocols that are allowed or denied access to resources. Default rules are created to allow TLS traffic to the Kubernetes API server. As you create services with load balancers, port mappings, or ingress routes, AKS automatically modifies the network security group for traffic to flow appropriately.
6466

67+
### Kubernetes network policy
68+
69+
To limit network traffic between pods in your cluster, AKS offers support for [Kubernetes network policies][network-policy]. With network policies, you can choose to allow or deny specific network paths within the cluster based on namespaces and label selectors.
70+
6571
## Kubernetes Secrets
6672

6773
A Kubernetes *Secret* is used to inject sensitive data into pods, such as access credentials or keys. You first create a Secret using the Kubernetes API. When you define your pod or deployment, a specific Secret can be requested. Secrets are only provided to nodes that have a scheduled pod that requires it, and the Secret is stored in *tmpfs*, not written to disk. When the last pod on a node that requires a Secret is deleted, the Secret is deleted from the node's tmpfs. Secrets are stored within a given namespace and can only be accessed by pods within the same namespace.
@@ -100,3 +106,6 @@ For additional information on core Kubernetes and AKS concepts, see the followin
100106
[operator-best-practices-cluster-security]: operator-best-practices-cluster-security.md
101107
[developer-best-practices-pod-security]:developer-best-practices-pod-security.md
102108
[nodepool-upgrade]: use-multiple-node-pools.md#upgrade-a-node-pool
109+
[authorized-ip-ranges]: api-server-authorized-ip-ranges.md
110+
[private-clusters]: private-clusters.md
111+
[network-policy]: use-network-policies.md

articles/automation/automation-child-runbooks.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,6 @@ ms.topic: conceptual
1010

1111
It is a recommended practice in Azure Automation to write reusable, modular runbooks with a discrete function that is called by other runbooks. A parent runbook often calls one or more child runbooks to perform required functionality. There are two ways to call a child runbook, and there are distinct differences that you should understand to be able to determine which is best for your scenarios.
1212

13-
>[!NOTE]
14-
>This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](automation-update-azure-modules.md).
15-
1613
## Invoking a child runbook using inline execution
1714

1815
To invoke a runbook inline from another runbook, use the name of the runbook and provide values for its parameters, just like you would use an activity or a cmdlet. All runbooks in the same Automation account are available to all others to be used in this manner. The parent runbook waits for the child runbook to complete before moving to the next line, and any output returns directly to the parent.

articles/automation/automation-config-aws-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,4 @@ After you have created and copied your AWS security keys, you need to create a C
2727

2828
## Next steps
2929

30-
* Review the solution article [Automating deployment of a VM in Amazon Web Services](automation-scenario-aws-deployment.md) to learn how to create runbooks to automate tasks in AWS.
30+
* Review [Automating deployment of a VM in Amazon Web Services](automation-scenario-aws-deployment.md) to learn how to create runbooks to automate tasks in AWS.

0 commit comments

Comments
 (0)