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/migrate/how-to-create-group-machine-dependencies-agentless.md
+1-36Lines changed: 1 addition & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -244,7 +244,6 @@ After you have performed the required steps to upgrade to the new dependency vis
244
244
> It's recommended to use **Option 1** above to switch to the new inventory view as you're able to filter servers where dependency analysis was auto-enabled and then directly review the dependency visualization. Old inventory view only provides option to visualize dependencies for servers where you had manually enabled the feature.
245
245
246
246
::: moniker range="migrate"
247
-
248
247
## Manage dependencies
249
248
250
249
Dependency analysis is auto-enabled on all discovered servers (upto 1000 servers per appliance)which have passed the validation checks. You may need to disable one or more of these servers in the following scenarios:
@@ -330,7 +329,6 @@ The different filters available for use in the command above are:
330
329
| Dependencies | Enabled / Disabled |
331
330
| PowerStatus | On / Off |
332
331
333
-
334
332
Some of the other fields are IP Address, osType, osName, osArchitecture, osVersion
335
333
336
334
You can find discovered servers for a specific appliance by using the command:
@@ -354,42 +352,9 @@ You need to follow the same steps to export the discovered servers as mentioned
354
352
In the following example, dependency analysis is being enabled on the list of servers in the input file ContosoDemo_VMs_Enable.csv.
Azure Migrate offers a Power BI template that you can use to visualize network connections of many servers at once, and filter by process and server. To visualize, load the Power BI with dependency data as per the below instructions.
361
-
362
-
### Log in to Azure
363
-
364
-
1. Log in to your Azure subscription using the Connect-AzAccount cmdlet.
365
-
`Connect-AzAccount`
366
-
367
-
If using Azure Government, use the following command.
1. Install the AzMig.Dependencies PowerShell module
373
-
`Install-Module .\AzMig.Dependencies`
374
-
1. Run the following command. This command downloads the dependencies data in a CSV and processes it to generate a list of unique dependencies that can be used for visualization in Power BI. In the example below the project name is ContosoDemoProject, and the resource group it belongs to be ContosoDemoRG. The dependencies are downloaded for servers discovered by ContosoApp. The unique dependencies are saved in ContosoDemo_Dependencies.csv
1. Load the downloaded dependency data in Power BI.
379
-
1. Open the template in Power BI.
380
-
1. Select Get Data on the tool bar.
381
-
1. Choose Text/CSV from Common data sources.
382
-
1. Choose the dependencies file downloaded.
383
-
1. Select Load.
384
-
You see a table is imported with the name of the CSV file. You can see the table in the fields bar on the right. Rename it to AzMig_Dependencies
385
-
1. Select refresh from the tool bar.
386
-
387
-
The Network Connections chart and the Source server name, Destination server name, Source process name, Destination process name slicers should light up with the imported data.
388
-
389
-
Visualize the map of network connections filtering by servers and processes. Save your file.
390
-
391
355
::: moniker-end
392
356
357
+
::: moniker range="migrate-classic"
393
358
## Disable auto-enabled dependency analysis using PowerShell
394
359
395
360
Dependency analysis is auto-enabled on all discovered servers which have passed the validation checks. You may need to disable one or more of these servers in the following scenarios:
0 commit comments