Skip to content

Sumit/modify day2 data - #31

Merged
Sophie Jorgensen (sophiejorgensen) merged 2 commits into
mainfrom
sumit/modify-day2-data
Oct 7, 2026
Merged

Sophie Jorgensen (sophiejorgensen) merged 2 commits into
mainfrom
sumit/modify-day2-data

Conversation

@sumitsengupta

Copy link
Copy Markdown
Contributor

Take out lab5 and lab6 of data mod - as these can either be not implemented or be tested in skillable environment.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

None

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The removed identity setup breaks Lab 06, and several migration, access-control, and documentation instructions are incorrect.

5 open findings
What changed in this PR

Streamlines the data-modernization lab by removing Challenges 5–6 and refining migration instructions.

Changes:

  • Expands assessment and SQL MI connection guidance.
  • Clarifies DMS backup and online migration steps.
  • Removes private-endpoint and application-readiness challenges.
File Description
labs/​day-2/​05-modernize-data/​README.md Revises and shortens the Lab 05 workflow.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.


#### Validate firewall access to SQL MI before begining.

Validate from the portal, that the NSG for the VNet that Azure SQL Managed Instance is allowing inbount access to port 3342. If not, add an inbound rule for port 3342. From the overview page of SQL MI, click on virtual network/subnet. On the subnet page, find the Network Security Group name. Pull up that NSG by name and add an imbound port rule like this:
ALTER ROLE db_datareader ADD MEMBER [caldova_retail_app];
ALTER ROLE db_datawriter ADD MEMBER [caldova_retail_app];
```
Wait till all transaction logs have all been restored and no files left ( as seen in azure storage ) to restore.
![Storage3](./images/Storage_3.png)

Once the storage account is created, you will need to grant to your current Azure user the permission to manage Blob containers. Do this via IAM. Assign the *Storage Blob Data Owner* role to your own Entra ID.
Once the storage account is created, you will need to grant to your current Azure user the permission to manage Blob containers. Do this via IAM. Assign the *Storage Blob Data Owner* (or Contributor) role to your own Entra ID.
4. What evidence is required before declaring the migration successful?
5. What would change for a production migration with minimal downtime?
6. Which steps should be automated for repeatable delivery?
#### Congratulations - you have migrated to Azure SQL
4. Connect to the target SQL MI using SSMS. Select the right option in SSMS when loging in. To find out the Entra ID to use for login, navigate from the portal to the deployed Azure SQL Managed Instance and go to Microsoft Entra ID on the left under settings. In this lab, this Entra ID is same as your Azure login - also shared under <b>"Resources"</b> section on the top.

![SQLMI_ENTRA](./images/sqlmi_entra.png)
7. Connect to the target SQL MI using SSMS. Notice that there are no databaes there.
@sophiejorgensen
Sophie Jorgensen (sophiejorgensen) merged commit 60b7822 into main Oct 7, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants