Azure AD Connect: Update PreferredDataLocation #4472
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@billmath, can you please review this change. |
|
#sign-off |
billmath
approved these changes
Jan 19, 2018
|
#sign-off |
ghost
merged commit 
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Discussed with @billmath before I made the change.
The information regarding PreferredDataLocation was missing important information and steps. With that added, it became too long in the current topic. It also didn't make sense since this feature was included in a conceptual topic, but it is a stand-alone feature. It was already on Bill's list of issues to fix later.
ToDo (for Bill). Add the new topic to the TOC.md.