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/hybrid/how-to-connect-install-prerequisites.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,9 @@ Before you install Azure AD Connect, there are a few things that you need.
43
43
* It is recommended to [enable the Active Directory recycle bin](how-to-connect-sync-recycle-bin.md).
44
44
45
45
### Azure AD Connect server
46
+
>[!IMPORTANT]
47
+
>The Azure AD Connect server contains critical identity data and should be treated as a Tier 0 component as documented in [the Active Directory administrative tier model](https://docs.microsoft.com/windows-server/identity/securing-privileged-access/securing-privileged-access-reference-material#ADATM_BM)
48
+
46
49
* Azure AD Connect cannot be installed on Small Business Server or Windows Server Essentials before 2019 (Windows Server Essentials 2019 is supported). The server must be using Windows Server standard or better.
47
50
* Installing Azure AD Connect on a Domain Controller is not recommended due to security practices and more restrictive settings that can prevent Azure AD Connect from installing correctly
48
51
* The Azure AD Connect server must have a full GUI installed. It is **not supported** to install on server core.
This article explains how to enable Azure Monitor for VMs (preview) for virtual machines or physical computers hosted in your datacenter or other cloud environment. At the end of this process you will have successfully begun monitoring your virtual machines in your environment and learn if they are experiencing any performance or availability issues.
22
+
This article explains how to enable Azure Monitor for VMs (preview) for virtual machines or physical computers hosted in your datacenter or other cloud environment. At the end of this process, you will have successfully begun monitoring your virtual machines in your environment and learn if they are experiencing any performance or availability issues.
23
23
24
-
Before getting started, be sure to review the [prerequisites](vminsights-enable-overview.md) and verify your subscription and resources meet the requirements. Review the requirements and deployment methods for the [Log Analytics Linux and Windows agent](../../log-analytics/log-analytics-agent-overview.md).
24
+
Before you get started, be sure to review the [prerequisites](vminsights-enable-overview.md) and verify that your subscription and resources meet the requirements. Review the requirements and deployment methods for the [Log Analytics Linux and Windows agent](../../log-analytics/log-analytics-agent-overview.md).
>The Azure Monitor for VMs Map Dependency agent doesn't transmit any data itself, and it doesn't require any changes to firewalls or ports. The Map data is always transmitted by the Log Analytics agent to the Azure Monitor service, either directly or through the [OMS Gateway](../../azure-monitor/platform/gateway.md) if your IT security policies don't allow computers on the network to connect to the internet.
29
+
>The Azure Monitor for VMs Map Dependency agent doesn't transmit any data itself, and it doesn't require any changes to firewalls or ports. The Map data is always transmitted by the Log Analytics agent to the Azure Monitor service, either directly or through the [Operations Management Suite gateway](../../azure-monitor/platform/gateway.md) if your IT security policies don't allow computers on the network to connect to the internet.
30
30
31
-
The tasks to complete this task are summarized as follows:
31
+
The steps to complete this task are summarized as follows:
32
32
33
-
1. Install Log Analytics agent for Windows or Linux. Before installing the agent, review the [Log Analytics agent overview](../platform/log-analytics-agent.md) article to understand system prerequisites and deployment methods.
33
+
1. Install Log Analytics agent for Windows or Linux. Before you install the agent, review the [Log Analytics agent overview](../platform/log-analytics-agent.md) article to understand system prerequisites and deployment methods.
34
34
35
35
2. Download and install the Azure Monitor for VMs Map Dependency agent for [Windows](https://aka.ms/dependencyagentwindows) or [Linux](https://aka.ms/dependencyagentlinux).
36
36
@@ -51,9 +51,9 @@ The following table highlights the parameters that are supported by setup for th
51
51
| /? | Returns a list of the command-line options. |
52
52
| /S | Performs a silent installation with no user interaction. |
53
53
54
-
For example, to run the installation program with the `/?` parameter, type**InstallDependencyAgent-Windows.exe /?**.
54
+
For example, to run the installation program with the `/?` parameter, enter**InstallDependencyAgent-Windows.exe /?**.
55
55
56
-
Files for the Windows Dependency agent are installed in *C:\Program Files\Microsoft Dependency Agent* by default. If the Dependency agent fails to start after setup is complete, check the logs for detailed error information. The log directory is *%Programfiles%\Microsoft Dependency Agent\logs*.
56
+
Files for the Windows Dependency agent are installed in *C:\Program Files\Microsoft Dependency Agent* by default. If the Dependency agent fails to start after setup is finished, check the logs for detailed error information. The log directory is *%Programfiles%\Microsoft Dependency Agent\logs*.
57
57
58
58
## Install the Dependency agent on Linux
59
59
The Dependency agent is installed on Linux servers from *InstallDependencyAgent-Linux64.bin*, a shell script with a self-extracting binary. You can run the file by using `sh` or add execute permissions to the file itself.
@@ -68,9 +68,9 @@ The Dependency agent is installed on Linux servers from *InstallDependencyAgent-
68
68
| -s | Perform a silent installation with no user prompts. |
69
69
| --check | Check permissions and the operating system, but don't install the agent. |
70
70
71
-
For example, to run the installation program with the `-help` parameter, type**InstallDependencyAgent-Linux64.bin -help**.
71
+
For example, to run the installation program with the `-help` parameter, enter**InstallDependencyAgent-Linux64.bin -help**.
72
72
73
-
Install the Linux Dependency agent as root by running the following command,`sh InstallDependencyAgent-Linux64.bin`.
73
+
Install the Linux Dependency agent as root by running the command `sh InstallDependencyAgent-Linux64.bin`.
74
74
75
75
If the Dependency agent fails to start, check the logs for detailed error information. On Linux agents, the log directory is */var/opt/microsoft/dependency-agent/log*.
76
76
@@ -85,18 +85,18 @@ Files for the Dependency agent are placed in the following directories:
If the Log Analytics workspace that's referenced by the solution isn't already configured to collect the performance counters required by the solution, you will need to enable them. You can do so in either of two ways:
88
+
If the Log Analytics workspace that's referenced by the solution isn't already configured to collect the performance counters required by the solution, you need to enable them. You can do so in one of two ways:
89
89
* Manually, as described in [Windows and Linux performance data sources in Log Analytics](../../azure-monitor/platform/data-sources-performance-counters.md)
90
-
* By downloading and running a PowerShell script that's available from [Azure PowerShell Gallery](https://www.powershellgallery.com/packages/Enable-VMInsightsPerfCounters/1.1)
90
+
* By downloading and running a PowerShell script that's available from the [Azure PowerShell Gallery](https://www.powershellgallery.com/packages/Enable-VMInsightsPerfCounters/1.1)
91
91
92
92
## Deploy Azure Monitor for VMs
93
93
This method includes a JSON template that specifies the configuration for enabling the solution components in your Log Analytics workspace.
94
94
95
-
If you're unfamiliar with deploying resources by using a template, see:
95
+
If you don't know how to deploy resources by using a template, see:
96
96
*[Deploy resources with Resource Manager templates and Azure PowerShell](../../azure-resource-manager/resource-group-template-deploy.md)
97
97
*[Deploy resources with Resource Manager templates and the Azure CLI](../../azure-resource-manager/resource-group-template-deploy-cli.md)
98
98
99
-
If you choose to use the Azure CLI, you first need to install and use the CLI locally. You must be running the Azure CLI version 2.0.27 or later. To identify your version, run `az --version`. If you need to install or upgrade the Azure CLI, see [Install the Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli).
99
+
To use the Azure CLI, you first need to install and use the CLI locally. You must be running the Azure CLI version 2.0.27 or later. To identify your version, run `az --version`. To install or upgrade the Azure CLI, see [Install the Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli).
100
100
101
101
### Create and execute a template
102
102
@@ -174,7 +174,7 @@ If you choose to use the Azure CLI, you first need to install and use the CLI lo
The configuration change can take a few minutes to complete. When it's complete, a message is displayed that's similar to the following and includes the result:
177
+
The configuration change can take a few minutes to finish. When it's finished, a message displays that's similar to the following and includes the result:
178
178
179
179
```powershell
180
180
provisioningState : Succeeded
@@ -183,4 +183,9 @@ If you choose to use the Azure CLI, you first need to install and use the CLI lo
183
183
184
184
## Next steps
185
185
186
-
Now that monitoring is enabled for your virtual machines, this information is available for analysis with Azure Monitor for VMs. To learn how to use the Health feature, see [View Azure Monitor for VMs Health](vminsights-health.md). To view discovered application dependencies, see [View Azure Monitor for VMs Map](vminsights-maps.md). To identify bottlenecks and overall utilization with your VMs performance, see [View Azure VM Performance](vminsights-performance.md), or to view discovered application dependencies, see [View Azure Monitor for VMs Map](vminsights-maps.md).
186
+
Now that monitoring is enabled for your virtual machines, this information is available for analysis with Azure Monitor for VMs.
187
+
188
+
- To learn how to use the Health feature, see [View Azure Monitor for VMs health](vminsights-health.md).
189
+
- To view discovered application dependencies, see [View Azure Monitor for VMs Map](vminsights-maps.md).
190
+
- To identify bottlenecks and overall utilization with your VM's performance, see [View Azure VM performance](vminsights-performance.md).
191
+
- To view discovered application dependencies, see [View Azure Monitor for VMs Map](vminsights-maps.md).
Copy file name to clipboardExpand all lines: articles/cognitive-services/cognitive-services-container-support.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
@@ -78,7 +78,7 @@ In addition, some containers are supported in Cognitive Services [**All-In-One o
78
78
Azure Cognitive Services containers are publicly available through your Azure subscription, and Docker container images can be pulled from either the Microsoft Container Registry or Docker Hub. You can use the [docker pull](https://docs.docker.com/engine/reference/commandline/pull/) command to download a container image from the appropriate registry.
79
79
80
80
> [!IMPORTANT]
81
-
> Currently, you must complete a sign-up process to access the following containers, in which you fill out and submit a questionnaire with questions about you, your company, and the use case for which you want to implement the containers. Once you're granted access and provided credentials, you can then pull the container images for the Face and Recognize Text containers from a private container registry hosted by Azure Container Registry.
81
+
> Currently, you must complete a sign-up process to access the following containers, in which you fill out and submit a questionnaire with questions about you, your company, and the use case for which you want to implement the containers. Once you're granted access and provided credentials, you can then pull the container images from a private container registry hosted by Azure Container Registry.
0 commit comments