Skip to content

Commit dea0077

Browse files
authored
Merge pull request #100395 from 928PJY/v3-migration-content-fix-invalid-bookmark
fix invalid bookmark
2 parents c48357b + a4c82cb commit dea0077

File tree

59 files changed

+66
-66
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

59 files changed

+66
-66
lines changed

articles/active-directory/authentication/howto-password-ban-bad-on-premises-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ During the audit stage, many organizations find out that:
3131

3232
It is also possible for stronger password validation to affect your existing Active Directory domain controller deployment automation. We recommend that at least one DC promotion and one DC demotion happen during the audit period evaluation in order to help uncover such issues in advance. For more information, see:
3333

34-
* [Ntdsutil.exe is unable to set a weak Directory Services Repair Mode password](howto-password-ban-bad-on-premises-troubleshoot.md##ntdsutilexe-fails-to-set-a-weak-dsrm-password)
34+
* [Ntdsutil.exe is unable to set a weak Directory Services Repair Mode password](howto-password-ban-bad-on-premises-troubleshoot.md#ntdsutilexe-fails-to-set-a-weak-dsrm-password)
3535
* [Domain controller replica promotion fails because of a weak Directory Services Repair Mode password](howto-password-ban-bad-on-premises-troubleshoot.md#domain-controller-replica-promotion-fails-because-of-a-weak-dsrm-password)
3636
* [Domain controller demotion fails due to a weak local Administrator password](howto-password-ban-bad-on-premises-troubleshoot.md#domain-controller-demotion-fails-due-to-a-weak-local-administrator-password)
3737

articles/active-directory/devices/troubleshoot-hybrid-join-windows-current.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ Applicable only for federated domain accounts.
244244
Reasons for failure:
245245

246246
- Unable to get an Access token silently for DRS resource.
247-
- Windows 10 devices acquire auth token from the federation service using Integrated Windows Authentication to an active WS-Trust endpoint. Details: [Federation Service Configuration](hybrid-azuread-join-manual.md##set-up-issuance-of-claims)
247+
- Windows 10 devices acquire auth token from the federation service using Integrated Windows Authentication to an active WS-Trust endpoint. Details: [Federation Service Configuration](hybrid-azuread-join-manual.md#set-up-issuance-of-claims)
248248

249249
**Common error codes:**
250250

articles/active-directory/hybrid/how-to-connect-install-custom.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ After entering the forest name and clicking **Add Directory**, a pop-up dialog
7777
| Option | Description |
7878
| --- | --- |
7979
| Create new account | Select this option if you want Azure AD Connect wizard to create the AD DS account required by Azure AD Connect for connecting to the AD forest during directory synchronization. When this option is selected, enter the username and password for an enterprise admin account. The enterprise admin account provided will be used by Azure AD Connect wizard to create the required AD DS account. You can enter the domain part in either NetBios or FQDN format, that is, FABRIKAM\administrator or fabrikam.com\administrator. |
80-
| Use existing account | Select this option if you want to provide an existing AD DS account to be used Azure AD Connect for connecting to the AD forest during directory synchronization. You can enter the domain part in either NetBios or FQDN format, that is, FABRIKAM\syncuser or fabrikam.com\syncuser. This account can be a regular user account because it only needs the default read permissions. However, depending on your scenario, you may need more permissions. For more information, see [Azure AD Connect Accounts and permissions](reference-connect-accounts-permissions.md##create-the-ad-ds-connector-account). |
80+
| Use existing account | Select this option if you want to provide an existing AD DS account to be used Azure AD Connect for connecting to the AD forest during directory synchronization. You can enter the domain part in either NetBios or FQDN format, that is, FABRIKAM\syncuser or fabrikam.com\syncuser. This account can be a regular user account because it only needs the default read permissions. However, depending on your scenario, you may need more permissions. For more information, see [Azure AD Connect Accounts and permissions](reference-connect-accounts-permissions.md#create-the-ad-ds-connector-account). |
8181

8282
![Connect Directory](./media/how-to-connect-install-custom/connectdir02.png)
8383

articles/active-directory/hybrid/how-to-connect-sso-quick-start.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -208,7 +208,7 @@ To test the feature for a specific user, ensure that all the following condition
208208
- The user signs in on a corporate device.
209209
- The device is joined to your Active Directory domain. The device _doesn't_ need to be [Azure AD Joined](../active-directory-azureadjoin-overview.md).
210210
- The device has a direct connection to your domain controller (DC), either on the corporate wired or wireless network or via a remote access connection, such as a VPN connection.
211-
- You have [rolled out the feature](##step-3-roll-out-the-feature) to this user through Group Policy.
211+
- You have [rolled out the feature](#step-3-roll-out-the-feature) to this user through Group Policy.
212212

213213
To test the scenario where the user enters only the username, but not the password:
214214
- Sign in to `https://myapps.microsoft.com/` in a new private browser session.

articles/automation/troubleshoot/onboarding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ Once you remove the solutions you can unlink your workspace. It is important to
153153
* Remove Update Deployments (Schedules) from your Automation Account
154154
* Start/Stop VMs during off-hours
155155
* Remove any locks on solution components in your Automation Account under **Settings** > **Locks**.
156-
* For additional steps to remove the Start/Stop VMs during off-hours solution see, [Remove the Start/Stop VM during off-hours solution](../automation-solution-vm-management.md##remove-the-solution).
156+
* For additional steps to remove the Start/Stop VMs during off-hours solution see, [Remove the Start/Stop VM during off-hours solution](../automation-solution-vm-management.md#remove-the-solution).
157157

158158
## <a name="mma-extension-failures"></a>MMA Extension failures
159159

articles/cognitive-services/LUIS/luis-concept-patterns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Learn pattern syntax from the [pattern syntax reference](reference-pattern-synta
6767
Learn more about patterns:
6868

6969
* [How to add patterns](luis-how-to-model-intent-pattern.md)
70-
* [How to add pattern.any entity](luis-how-to-add-entities.md##add-a-patternany-entity)
70+
* [How to add pattern.any entity](luis-how-to-add-entities.md#add-a-patternany-entity)
7171
* [Patterns Syntax](reference-pattern-syntax.md)
7272

7373
> [!div class="nextstepaction"]

articles/cognitive-services/LUIS/luis-container-howto.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Once the container is on the [host computer](#the-host-computer), use the follow
7979

8080
1. [Export package](#export-packaged-app-from-luis) for container from LUIS portal or LUIS APIs.
8181
1. Move package file into the required **input** directory on the [host computer](#the-host-computer). Do not rename, alter, overwrite, or decompress the LUIS package file.
82-
1. [Run the container](##run-the-container-with-docker-run), with the required _input mount_ and billing settings. More [examples](luis-container-configuration.md#example-docker-run-commands) of the `docker run` command are available.
82+
1. [Run the container](#run-the-container-with-docker-run), with the required _input mount_ and billing settings. More [examples](luis-container-configuration.md#example-docker-run-commands) of the `docker run` command are available.
8383
1. [Querying the container's prediction endpoint](#query-the-containers-prediction-endpoint).
8484
1. When you are done with the container, [import the endpoint logs](#import-the-endpoint-logs-for-active-learning) from the output mount in the LUIS portal and [stop](#stop-the-container) the container.
8585
1. Use LUIS portal's [active learning](luis-how-to-review-endpoint-utterances.md) on the **Review endpoint utterances** page to improve the app.

articles/cognitive-services/LUIS/luis-tutorial-bot-csharp-appinsights.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ In order to add data to application insights, you need the instrumentation key.
157157
1. In Visual Studio, build and run the bot.
158158
1. Start the bot emulator and open the bot. This [step](luis-csharp-tutorial-bf-v4.md#use-the-bot-emulator-to-test-the-bot) is provided in the previous tutorial.
159159

160-
1. Ask the bot a question. This [step](luis-csharp-tutorial-bf-v4.md##use-the-bot-emulator-to-test-the-bot) is provided in the previous tutorial.
160+
1. Ask the bot a question. This [step](luis-csharp-tutorial-bf-v4.md#use-the-bot-emulator-to-test-the-bot) is provided in the previous tutorial.
161161

162162
## View LUIS entries in Application Insights
163163

articles/cognitive-services/LUIS/reference-pattern-syntax.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ Punctuation marks (`?`, `!`, `.`) should be ignored and you need to ignore them
137137
Learn more about patterns:
138138

139139
* [How to add patterns](luis-how-to-model-intent-pattern.md)
140-
* [How to add pattern.any entity](luis-how-to-add-entities.md##add-a-patternany-entity)
140+
* [How to add pattern.any entity](luis-how-to-add-entities.md#add-a-patternany-entity)
141141
* [Patterns Concepts](luis-concept-patterns.md)
142142

143143
Understand how [sentiment](luis-reference-prebuilt-sentiment.md) is returned in the .json response.

articles/cognitive-services/LUIS/tutorial-publish-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Because it is a publish setting, you do not see it labeled on the intents or ent
125125

126126
## Related information
127127

128-
* Sentiment analysis is provided by Cognitive Service [Text Analytics](../Text-Analytics/index.yml). The feature is restricted to Text Analytics [supported languages](luis-language-support.md##languages-supported).
128+
* Sentiment analysis is provided by Cognitive Service [Text Analytics](../Text-Analytics/index.yml). The feature is restricted to Text Analytics [supported languages](luis-language-support.md#languages-supported).
129129
* [How to train](luis-how-to-train.md)
130130
* [How to publish](luis-how-to-publish-app.md)
131131
* [How to test in LUIS portal](luis-interactive-test.md)

0 commit comments

Comments
 (0)