You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/identity-provider-azure-ad-multi-tenant-custom.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ manager: celestedg
9
9
ms.service: active-directory
10
10
ms.workload: identity
11
11
ms.topic: conceptual
12
-
ms.date: 02/06/2020
12
+
ms.date: 02/10/2020
13
13
ms.author: marsma
14
14
ms.subservice: B2C
15
15
---
@@ -46,6 +46,19 @@ To enable sign-in for users from a specific Azure AD organization, you need to r
46
46
1. Select **Certificates & secrets**, and then select **New client secret**.
47
47
1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **Value** of the secret for use in a later step.
48
48
49
+
## Configuring optional claims
50
+
51
+
If you want to get the `family_name` and `given_name` claims from Azure AD, you can configure optional claims for your application in the Azure portal UI or application manifest. For more information, see [How to provide optional claims to your Azure AD app](../active-directory/develop/active-directory-optional-claims.md).
52
+
53
+
1. Sign in to the [Azure portal](https://portal.azure.com). Search for and select **Azure Active Directory**.
54
+
1. From the **Manage** section, select **App registrations**.
55
+
1. Select the application you want to configure optional claims for in the list.
56
+
1. From the **Manage** section, select **Token configuration (preview)**.
57
+
1. Select **Add optional claim**.
58
+
1. Select the token type you want to configure.
59
+
1. Select the optional claims to add.
60
+
1. Click **Add**.
61
+
49
62
## Create a policy key
50
63
51
64
You need to store the application key that you created in your Azure AD B2C tenant.
@@ -60,19 +73,6 @@ You need to store the application key that you created in your Azure AD B2C tena
60
73
1. For **Key usage**, select `Signature`.
61
74
1. Select **Create**.
62
75
63
-
## Configuring optional claims
64
-
65
-
If you want to get the `family_name` and `given_name` claims from Azure AD, you can configure optional claims for your application in the Azure portal UI or application manifest. For more information, see [How to provide optional claims to your Azure AD app](../active-directory/develop/active-directory-optional-claims.md).
66
-
67
-
1. Sign in to the [Azure portal](https://portal.azure.com). Search for and select **Azure Active Directory**.
68
-
1. From the **Manage** section, select **App registrations**.
69
-
1. Select the application you want to configure optional claims for in the list.
70
-
1. From the **Manage** section, select **Token configuration (preview)**.
71
-
1. Select **Add optional claim**.
72
-
1. Select the token type you want to configure.
73
-
1. Select the optional claims to add.
74
-
1. Click **Add**.
75
-
76
76
## Add a claims provider
77
77
78
78
If you want users to sign in by using Azure AD, you need to define Azure AD as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify that a specific user has authenticated.
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/application-proxy-integrate-with-power-bi.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,9 +135,6 @@ Before the Power BI mobile app can connect and access Report Services, you must
135
135
136
136
## Step 5: Configure Intune policy for managed devices (optional)
137
137
138
-
> [!NOTE]
139
-
> This functionality is currently only available on iOS.
140
-
141
138
You can use Microsoft Intune to manage the client apps that your company's workforce uses. Intune allows you to use capabilities such as data encryption and additional access requirements. To learn more about app management through Intune, see Intune App Management. To enable the Power BI mobile application to work with the Intune policy, use the following steps.
142
139
143
140
1. Go to **Azure Active Directory** and then **App Registrations**.
Copy file name to clipboardExpand all lines: articles/aks/configure-azure-cni.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,9 +48,9 @@ The IP address plan for an AKS cluster consists of a virtual network, at least o
48
48
| --------- | ------------- |
49
49
| Virtual network | The Azure virtual network can be as large as /8, but is limited to 65,536 configured IP addresses. |
50
50
| Subnet | Must be large enough to accommodate the nodes, pods, and all Kubernetes and Azure resources that might be provisioned in your cluster. For example, if you deploy an internal Azure Load Balancer, its front-end IPs are allocated from the cluster subnet, not public IPs. The subnet size should also take into account upgrade operations or future scaling needs.<p />To calculate the *minimum* subnet size including an additional node for upgrade operations: `(number of nodes + 1) + ((number of nodes + 1) * maximum pods per node that you configure)`<p/>Example for a 50 node cluster: `(51) + (51 * 30 (default)) = 1,581` (/21 or larger)<p/>Example for a 50 node cluster that also includes provision to scale up an additional 10 nodes: `(61) + (61 * 30 (default)) = 1,891` (/21 or larger)<p>If you don't specify a maximum number of pods per node when you create your cluster, the maximum number of pods per node is set to *30*. The minimum number of IP addresses required is based on that value. If you calculate your minimum IP address requirements on a different maximum value, see [how to configure the maximum number of pods per node](#configure-maximum---new-clusters) to set this value when you deploy your cluster. |
51
-
| Kubernetes service address range | This range should not be used by any network element on or connected to this virtual network. Service address CIDR must be smaller than /12. |
51
+
| Kubernetes service address range | This range should not be used by any network element on or connected to this virtual network. Service address CIDR must be smaller than /12. You can reuse this range across different AKS clusters. |
52
52
| Kubernetes DNS service IP address | IP address within the Kubernetes service address range that will be used by cluster service discovery (kube-dns). Don't use the first IP address in your address range, such as .1. The first address in your subnet range is used for the *kubernetes.default.svc.cluster.local* address. |
53
-
| Docker bridge address | The Docker bridge network address represents the default *docker0* bridge network address present in all Docker installations. While *docker0* bridge is not used by AKS clusters or the pods themselves, you must set this address to continue to support scenarios such as *docker build* within the AKS cluster. It is required to select a CIDR for the Docker bridge network address because otherwise Docker will pick a subnet automatically which could conflict with other CIDRs. You must pick an address space that does not collide with the rest of the CIDRs on your networks, including the cluster's service CIDR and pod CIDR. Default of 172.17.0.1/16. |
53
+
| Docker bridge address | The Docker bridge network address represents the default *docker0* bridge network address present in all Docker installations. While *docker0* bridge is not used by AKS clusters or the pods themselves, you must set this address to continue to support scenarios such as *docker build* within the AKS cluster. It is required to select a CIDR for the Docker bridge network address because otherwise Docker will pick a subnet automatically which could conflict with other CIDRs. You must pick an address space that does not collide with the rest of the CIDRs on your networks, including the cluster's service CIDR and pod CIDR. Default of 172.17.0.1/16. You can reuse this range across different AKS clusters. |
After you set up integration with Azure Monitor logs for your Automation State Configuration data, a
75
-
**Log search** button will appear on the **DSC Nodes** blade of your automation account. Click the
76
-
**Log Search** button to view the logs for DSC node data.
74
+
After you set up integration with Azure Monitor logs for your Automation State Configuration data, they can be viewed by selecting **Logs** in the **Monitoring** section in the left pane of the State Configuration (DSC) page.
You can also view the logs by searching in Azure Monitor logs. See [Find data using log searches](https://docs.microsoft.com/azure/azure-monitor/log-query/log-query-overview). Type the following query to find your State Configuration logs.
92
87
93
-
You can also narrow the query by the operation name. For example:
Copy file name to clipboardExpand all lines: articles/automation/automation-windows-hrw-install.md
+23-19Lines changed: 23 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ ms.topic: conceptual
10
10
11
11
You can use the Hybrid Runbook Worker feature of Azure Automation to run runbooks directly on the computer that's hosting the role and against resources in the environment to manage those local resources. Runbooks are stored and managed in Azure Automation and then delivered to one or more designated computers. This article describes how to install the Hybrid Runbook Worker on a Windows machine.
12
12
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.3.0). For Az module installation instructions, see [Install the Azure PowerShell module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.4.0).
15
+
13
16
## Installing the Windows Hybrid Runbook Worker
14
17
15
18
To install and configure a Windows Hybrid Runbook Worker, you can use one of the three following methods:
@@ -25,12 +28,12 @@ To install and configure a Windows Hybrid Runbook Worker, you can use one of the
25
28
26
29
The minimum requirements for a Windows Hybrid Runbook Worker are:
27
30
28
-
* Windows Server 2012 or later.
29
-
* Windows PowerShell 5.1 or later ([download WMF 5.1](https://www.microsoft.com/download/details.aspx?id=54616)).
30
-
* .NET Framework 4.6.2 or later.
31
-
* Two cores.
32
-
* 4 GB of RAM.
33
-
* Port 443 (outbound).
31
+
* Windows Server 2012 or later
32
+
* Windows PowerShell 5.1 or later ([download WMF 5.1](https://www.microsoft.com/download/details.aspx?id=54616))
33
+
* .NET Framework 4.6.2 or later
34
+
* Two cores
35
+
* 4 GB of RAM
36
+
* Port 443 (outbound)
34
37
35
38
To get more networking requirements for the Hybrid Runbook Worker, see [Configuring your network](automation-hybrid-runbook-worker.md#network-planning).
36
39
@@ -45,17 +48,18 @@ After you successfully deploy a runbook worker, review [Run runbooks on a Hybrid
45
48
46
49
Perform the following steps to automate the installation and configuration of the Windows Hybrid Worker role:
47
50
48
-
1. Download the New-OnPremiseHybridWorker.ps1 script from the [PowerShell Gallery](https://www.powershellgallery.com/packages/New-OnPremiseHybridWorker) directly from the computer running the Hybrid Runbook Worker role or from another computer in your environment. Copy the script to the worker.
49
-
50
-
The New-OnPremiseHybridWorker.ps1 script requires the following parameters during execution:
51
+
1. Download the New-OnPremiseHybridWorker.ps1 script from the
52
+
[PowerShell Gallery](https://www.powershellgallery.com/packages/New-OnPremiseHybridWorker) directly from the computer running the Hybrid Runbook Worker role or from another computer in your environment. Copy the script to the worker. The New-OnPremiseHybridWorker.ps1 script requires the following parameters during execution:
51
53
52
-
**AutomationAccountName* (mandatory): The name of your Automation account.
53
54
**AAResourceGroupName* (mandatory): The name of the resource group that's associated with your Automation account.
54
55
**OMSResourceGroupName* (optional): The name of the resource group for the Log Analytics workspace. If this resource group is not specified, *AAResourceGroupName* is used.
55
-
**HybridGroupName* (mandatory): The name of a Hybrid Runbook Worker group that you specify as a target for the runbooks that support this scenario.
56
-
**SubscriptionID* (mandatory): The Azure subscription ID that your Automation account is in.
56
+
**SubscriptionID* (mandatory): The Azure subscription ID that your Automation Account is in.
57
+
**TenantID* (optional): The identifier of the tenant organization associated with your Automation Account.
57
58
**WorkspaceName* (optional): The Log Analytics workspace name. If you don't have a Log Analytics workspace, the script creates and configures one.
58
-
59
+
**AutomationAccountName* (mandatory): The name of your Automation Account.
60
+
**HybridGroupName* (mandatory): The name of a Hybrid Runbook Worker group that you specify as a target for the runbooks that support this scenario.
61
+
**Credential* (optional): The credentials to use when logging in to the Azure environment.
62
+
59
63
> [!NOTE]
60
64
> When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
61
65
>
@@ -75,7 +79,7 @@ Perform the following steps to automate the installation and configuration of th
75
79
76
80
4. You're prompted to agree to install NuGet, and you're prompted to authenticate with your Azure credentials.
77
81
78
-
5. After the script is finished, the **Hybrid Worker Groups** page shows the new group and the number of members. If it's an existing group, the number of members is incremented. You can select the group from the list on the **Hybrid Worker Groups** page and select the **Hybrid Workers** tile. On the **Hybrid Workers** page, you see each member of the group listed.
82
+
5. After the script is finished, the **Hybrid Worker Groups** page shows the new group and the number of members. If it's an existing group, the number of members is incremented. You can select the group from the list on the **Hybrid Worker Groups**page and select the **Hybrid Workers** tile. On the **Hybrid Workers** page, you see each member of the group listed.
79
83
80
84
### Manual deployment
81
85
@@ -91,10 +95,10 @@ If you don't already have a Log Analytics workspace, first review the [Azure Mon
91
95
92
96
The Automation solution adds functionality for Azure Automation, including support for Hybrid Runbook Worker. When you add the solution to your Log Analytics workspace, it automatically pushes worker components to the agent computer that you will install in the next step.
93
97
94
-
To add the **Automation** solution to your workspace, run the following PowerShell.
98
+
To add the **Automation** solution to your workspace, run the following PowerShell cmdlet.
#### 3. Install the Log Analytics agent for Windows
@@ -103,15 +107,15 @@ The Log Analytics agent for Windows connects computers to an Azure Monitor Log A
103
107
104
108
To install the agent on the computer, follow the instructions at [Connect Windows computers to Azure Monitor logs](../log-analytics/log-analytics-windows-agent.md). You can repeat this process for multiple computers to add multiple workers to your environment.
105
109
106
-
When the agent has successfully connected to your Log Analytics workspace, after a few minutes you can run the following query to verify it is sending heartbeat data to the workspace:
110
+
When the agent has successfully connected to your Log Analytics workspace after a few minutes, you can run the following query to verify that it is sending heartbeat data to the workspace:
107
111
108
112
```kusto
109
113
Heartbeat
110
114
| where Category == "Direct Agent"
111
115
| where TimeGenerated > ago(30m)
112
116
```
113
117
114
-
In the search results returned, you should see heartbeat records for the computer indicating it is connected and reporting to the service. The heartbeat record is forwarded from every agent by default to its assigned workspace. You can verify that the agent has correctly downloaded the Automation solution when it has a folder called **AzureAutomationFiles** in C:\Program Files\Microsoft Monitoring Agent\Agent. To confirm the version of the Hybrid Runbook Worker, you can browse to C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\ and note the \\*version* subfolder.
118
+
In the search results returned, you should see heartbeat records for the computer indicating it is connected and reporting to the service. The heartbeat record is forwarded from every agent by default to its assigned workspace. You can verify that the agent has correctly downloaded the Automation solution when it has a folder called **AzureAutomationFiles** in C:\Program Files\Microsoft Monitoring Agent\Agent. To confirm the version of the Hybrid Runbook Worker, browse to C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\ and note the \\*version* subfolder.
115
119
116
120
#### 4. Install the runbook environment and connect to Azure Automation
117
121
@@ -146,7 +150,7 @@ Runbooks can use any of the activities and cmdlets defined in the modules that a
146
150
147
151
Because the primary purpose of the Hybrid Runbook Worker feature is to manage local resources, you most likely need to install the modules that support these resources. For information on installing Windows PowerShell modules, see [Installing Modules](/powershell/scripting/developer/windows-powershell).
148
152
149
-
Modules that are installed must be in a location referenced by the **PSModulePath** environment variable so that the hybrid worker can automatically import them. For more information, see [Modifying the PSModulePath Installation Path](/powershell/scripting/developer/windows-powershell).
153
+
Modules that are installed must be in a location referenced by the **PSModulePath**environment variable so that the hybrid worker can automatically import them. For more information, see [Modifying the PSModulePath Installation Path](/powershell/scripting/developer/windows-powershell).
0 commit comments