Skip to content

Commit 0a55117

Browse files
committed
Resolve afternoon publish PR warnings 2
1 parent 1870adc commit 0a55117

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/troubleshoot/start-stop-vm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ This error can be caused by one of the following reasons:
131131

132132
Review the following list for potential solutions to your problem or places to look:
133133

134-
* When using the [sequence scenario](../automation-solution-vm-management.md#startstop-vms-during-off-hours-solution-in-azure-automation) of the Start/Stop VM during off hours solution, you must make sure each VM you want to start or stop has the proper tag. Make sure the VMs that you want to start have the `sequencestart` tag and the VMs you want to stop have the `sequencestop` tag. Both tags require a positive integer value. You can use a query similar to the following example to look for all the VMs with the tags and their values.
134+
* When using the [sequence scenario](../automation-solution-vm-management.md) of the Start/Stop VM during off hours solution, you must make sure each VM you want to start or stop has the proper tag. Make sure the VMs that you want to start have the `sequencestart` tag and the VMs you want to stop have the `sequencestop` tag. Both tags require a positive integer value. You can use a query similar to the following example to look for all the VMs with the tags and their values.
135135

136136
```powershell-interactive
137137
Get-AzureRmResource | ? {$_.Tags.Keys -contains "SequenceStart" -or $_.Tags.Keys -contains "SequenceStop"} | ft Name,Tags
@@ -181,7 +181,7 @@ Take the following steps to ensure that the solution is configured correctly.
181181
2. Make sure the resource groups for the VMs to be started or stopped are in the `External_Start_ResourceGroupNames` or `External_Stop_ResourceGroupNames` variables, depending on your situation.
182182
3. Test your changes by executing the `SequencedStartStop_Parent` runbook with the WHATIF parameter set to True to preview your changes.
183183

184-
For more detailed and additional instructions on how to use the solution to start and stop VMs in sequence, see [Start/Stop VMs in sequence](../automation-solution-vm-management.md#startstop-vms-during-off-hours-solution-in-azure-automation).
184+
For more detailed and additional instructions on how to use the solution to start and stop VMs in sequence, see [Start/Stop VMs in sequence](../automation-solution-vm-management.md).
185185

186186
## <a name="403"></a>Scenario: Start/Stop VM job fails with 403 forbidden status
187187

0 commit comments

Comments
 (0)