Update DP600 lab instructions to match current Fabric interface

[Copilot]

Several DP600 labs reference outdated Fabric UI terminology and omit handling for interface behaviors that have changed (auto-attached destinations, renamed activities, missing credential prompts).

Lab 04 — Copy Data / Copy Job terminology

• Added a note that newer Fabric may surface the copy assistant as Copy job instead of Copy Data; wizard steps are identical either way
• Updated the post-wizard result description to reflect both possible activity labels

Lab 05 — Lakehouse auto-attachment + stale "experience" reference

• Added a note that when Dataflow Gen2 is created from within a lakehouse (Get data > New Dataflow Gen2), the lakehouse is auto-attached as the default destination — Add data destination will be grayed out. Directs users to click the existing destination icon to reach the settings step
• Removed the reference to "Data Factory experience" (Fabric now uses workloads); replaced with direct + New item > Data pipeline navigation

Lab 16 — PBIT open prompts

• Added a note after opening the .pbit file to handle two common prompts: sign-in with org credentials and the privacy levels dialog
• Fixed awkward phrasing can you choose Don't save → choose Don't save
• Changed Load the data and open the report → Select **Load** to load the data and open the report (verb-first instruction)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Issue with DP600 Labs instructions</issue_title>
<issue_description>My issue is that for most of the DP600 labs, instructions doesn't match with the interfce. For instance for lab number 05: "Create and use Dataflows (Gen2) in Microsoft Fabric", steps like creating a workspace, lakehouse, adding a lakehouse to a dataflow are extremely confusing. Now we don't have experiences in Fabric; we have workloads. But instructions say go to Data Engineering experience. Also, when we are creating dataflows within the lakehouse, lakehouse gets attached automatically as a default destination. But instructions are instructing to add lakehouse, while its disabled since its already attached. So I have to reiterate it multiple times to students.

The issue is not only in lab 05, same issue persists in lab 04. Now copy assisstant doesn't use copy data activity; it uses copy job. Again mismatch with instrcutions and fabric interface.

Same for power bi labs as well. Many instructions are missing. Like for lab 10 and lab 12. Lab 10 assumes, people knows power BI while in Lab 12, it skips instructions on how to login to server while we are opening PBIT file.</issue_description>

<agent_instructions>Identify where to improve the readability for the instructions. Start with verbs first when adding new instructions to follow, even if using directional language to explain how to find the feature.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@weslbo @arundba5 Thank you for your suggestions. We will review those and make updates where necessary. @AngieRudduck > Same for power bi labs as well. Many instructions are missing. Like for lab 10 and lab 12. Lab 10 assumes, people knows power BI while in Lab 12, it skips instructions on how to login to server while we are opening PBIT file.

Thank you for this feedback. PL-300 is highly recommended for DP-600, and it is expected that learners have experience using Power BI. We will review the instructions to see where clarity can be added, but we won't introduce introductory steps to navigate Power BI Desktop.</comment_new>

• Fixes Issue with DP600 Labs instructions #324

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[v-mohamrafi]

Lab 04 — Copy Data / Copy Job terminology
It's similar omission Fix lab 04: replace Copy Data wizard with manual activity steps
#350
Replicated with same raised issue.
Removing instructions : As copy data wizard starts automatically.
If the Copy Data wizard doesn’t open automatically, select Copy Data > Use copy assistant in the pipeline editor page.

Existing
Lab 05 — Lakehouse auto-attachment + stale "experience" reference

1. In the home page for your lakehouse, select Get data > New Dataflow Gen2. After a few seconds, the Power Query editor for your new dataflow opens as shown here.

Replacement required

1. Directly click on New Dataflow Gen2 in main screen ==> Followed with New Dataflow Gen2
   to prepare clean, transform, and ingest data.

Lab 16 — PBIT open prompts
Escalating to GTLSkillable as VM's not working followed up to the team.
required further to cross verify as the csv resources under VM. to review further