Skip to content

Commit 1bd59cd

Browse files
committed
minor edit
1 parent 2294a08 commit 1bd59cd

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/migrate/how-to-create-group-machine-dependencies-agentless.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -102,13 +102,13 @@ On reviewing the **Dependencies** column for any server, you see one of the foll
102102
3. **Validation failed:** when the validation checks on the server have failed. You can select the status to review error message which would mostly be related to missing prerequisites like insufficient credential permissions or invalid credentials etc.
103103

104104
::: moniker range="migrate"
105-
After the validation succeeds, dependency analysis are auto-enabled and you see one of the following status:
105+
After the validation succeeds, dependency analysis are auto-enabled and you see one of the following status:
106106
::: moniker-end
107107

108-
- **View dependencies:** when validation checks have passed and the dependency analysis has been enabled. You can select this to go to the new visualization and review dependencies for this server.
108+
4. **View dependencies:** when validation checks have passed and the dependency analysis has been enabled. You can select this to go to the new visualization and review dependencies for this server.
109109
::: moniker range="migrate"
110-
- **Not initiated:** when dependency analysis couldn't be enabled as Azure Migrate has reached the scale limit of 1,000 servers per appliance for auto-enablement. If you want to perform dependency analysis on the specific servers, you can manually disable it on the other auto-enabled servers and enable for the ones you need by using the PowerShell module.
111-
- **Disabled:** when dependency analysis has been manually disabled by you on this server using the PowerShell module. You can re-enable it any-time using the same PowerShell module.
110+
5. **Not initiated:** when dependency analysis couldn't be enabled as Azure Migrate has reached the scale limit of 1,000 servers per appliance for auto-enablement. If you want to perform dependency analysis on the specific servers, you can manually disable it on the other auto-enabled servers and enable for the ones you need by using the PowerShell module.
111+
6. **Disabled:** when dependency analysis has been manually disabled by you on this server using the PowerShell module. You can re-enable it any-time using the same PowerShell module.
112112
::: moniker-end
113113

114114
## Visualize dependencies

0 commit comments

Comments
 (0)