Feature/vvereen direct lake docs

[vvereen]

Thank you for contributing to Microsoft Fabric documentation

Fill out these items before submitting your pull request:

If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.

https://dev.azure.com/powerbi/Power%20BI/_workitems/edit/2101137

Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.

Kelly Gremban

For internal Microsoft contributors, check off these quality control items as you go

• 1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.

• 2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).

• 3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.

• 4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.

• 5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing #sign-off in a new comment in the Pull Request. If you need to cancel that sign-off, type #hold-off instead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.

Merge and publish

• After you #sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.
• The review team will use the comments section in the PR to provide feedback if changes are needed. Address any blocking issues and sign off again to request another review.
• Once all feedback is resolved, you can #sign-off again. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).
• From the main branch, the change is merged into the live branch several times a day to publish it to the public learn.microsoft.com site.

[learn-build-service-prod]

Learn Build status updates of commit 0c9ed1c:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/fundamentals/direct-lake-how-it-works.md	✅Succeeded
docs/fundamentals/media/direct-lake-how-it-works/direct-lake-behavior-setting.png	✅Succeeded

For more details, please refer to the build report.

[vvereen]

@microsoft-github-policy-service agree [company="{Microsoft}"]

[learn-build-service-prod]

Learn Build status updates of commit 0c9ed1c:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/fundamentals/direct-lake-how-it-works.md	✅Succeeded
docs/fundamentals/media/direct-lake-how-it-works/direct-lake-behavior-setting.png	✅Succeeded

For more details, please refer to the build report.

[v-regandowner]

Hi @vvereen - It looks like you accidentally opened this PR in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

**

@kgremban

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[microsoft-github-policy-service]

@vvereen please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

[kgremban]

Approved, but some changes suggested to improve formatting and clarity.

[learn-build-service-prod]

Learn Build status updates of commit 746bba2:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/fundamentals/direct-lake-how-it-works.md	✅Succeeded
docs/fundamentals/media/direct-lake-how-it-works/direct-lake-behavior-setting.png	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit fd87e1b:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/fundamentals/direct-lake-how-it-works.md	✅Succeeded
docs/fundamentals/media/direct-lake-how-it-works/direct-lake-behavior-setting.png	✅Succeeded

For more details, please refer to the build report.

[maqister]

If you need to avoid fallback entirely, consider using Direct Lake on OneLake.

a bit weird sentence if i am being honest, best if we remove it entirely, in this case less is more :)

[vvereen]

Agreed, we can remove it.

[maqister]

not true

[vvereen]

I can remove rows 100 & 101, are the rest are still accurate? Apologies pulled these two from community blog posts.

[maqister]

those are conditions for using VertiPlans in DirectLake SQL.. it miscommunicates things to customers.

[vvereen]

Would naming the section "Conditions for avoiding DirectQuery fallback" be better?

[vvereen]

Hi @vvereen - It looks like you accidentally opened this PR in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

**

@kgremban

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

@v-regandowner, @kgremban Apologies, I have not used this process before but will ensure to use the Private Repo next time. As there are changes needed and potential new ownership, would it be best if we close and reopen on the Private Repo?

[v-dirichards]

Hi @vvereen - It looks like you accidentally opened this PR in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!
**
@kgremban
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

@v-regandowner, @kgremban Apologies, I have not used this process before but will ensure to use the Private Repo next time. As there are changes needed and potential new ownership, would it be best if we close and reopen on the Private Repo?

@vvereen It'd be best to have these moved to private so the content can be staged and validated by the current validation rules.

After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.

cc: @kgremban

[learn-build-service-prod]

Learn Build status updates of commit bb38f83:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/fundamentals/direct-lake-how-it-works.md	✅Succeeded
docs/fundamentals/media/direct-lake-how-it-works/direct-lake-behavior-setting.png	✅Succeeded

For more details, please refer to the build report.