There is no indication in the automatic deployment guide that the TailspinToys.bak file on the server C: drive must be restored before starting the HOL.

It's mentioned in the manual setup guide, but not the automatic one.

https://github.com/microsoft/MCW-Migrating-SQL-databases-to-Azure/blob/master/Hands-on%20lab/Appendix-A

Needs a '.md' to the end of the url.

Thanks,
Anna

There is a typing error of step6 of the step to step document,
Server name: Select SQLSERVER200. >> should be SQLSERVER2008.
Otherwise, it will show

Error:40
'Connection to the server failed.
Validator 'Microsoft.SqlServer.Migration.Core.Validators.SupportedDatabaseEnvironmentValidator' failed to validate data.'

Opening new issue because the root cause is different than the other SQLMI issue.

{ "code": "DeploymentFailed", "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.", "details": [ { "code": "Conflict", "message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"**_VnetSubnetConflictWithIntendedPolicy_**\",\r\n \"message\": \"**_Precondition failed_**.. (https://go.microsoft.com/fwlink/?linkid=871071)\"\r\n }\r\n ]\r\n }\r\n}" } ] }

Error below:

Error Detail
A scenario reported an unknown error.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

Please advise

I've attempted to deploy the ARM template, but receive the following error message after about 30 minutes:

"The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the server name, database name and activity ID."

However, after the ARM template deployment completely fails, I can manually deploy the SQL MI instance without issues. Has anyone else had this issue? My subscription core quota is high enough and I'm accepting all the ARM template defaults before deployment.

Please reach out if you need more information.

Task 3, Step 5 asks you to connect to the SQL Server as WorkshopUser, but the the connection fails.

I received this information via Teams chat. Creating a GitHub issue so it can be reviewed and addressed. Thank you!

Seems like some information in this doc is not correct - there is no need to have owner role in the resource group:

To migrate, the required permission is contributor role in sub, as specified in this official doc: https://docs.microsoft.com/en-au/azure/dms/tutorial-sql-server-managed-instance-online

Azure Database Migration Service requires the Contributor permission on the subscription for the specified Application ID. Alternatively, you can create custom roles that grant the specific permissions that Azure Database Migration Service requires. For step-by-step guidance about using custom roles, see the article Custom roles for SQL Server to SQL Managed Instance online migrations.

Unable to save point-to-site configuration.

Here is what I input.

• Address pool: 192.168.0.0/16
• Tunnel type: Select SSTP (SSL).
• Authentication type: Choose Azure certificate

When I followed the instruction 'Excercise4>Task1> 3 ' Save button is disabled.

Do I need to add Root certificates?

The ARM template for before HOL fails with below error, replicated multiple times in different subscription

{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VnetSubnetConflictWithIntendedPolicy",\r\n "message": "Route Table. (https://go.microsoft.com/fwlink/?linkid=871071)"\r\n }\r\n ]\r\n }\r\n}"
}
]
}

This workshop is scheduled for a January 2020 content update. Please review the workshop and provide recommended changes for SME review.

Created on the behalf of Tim Henning. I will soon resolve this issue. Hereinafter content is from Tim's email.

We need someone to be able to follow the instructions and run through the lab. Old Azure images will need to be updated. Small technical fixes may need to be applied. (less than about 1 hour, otherwise we need to go back to MS). Instructions may need to be updated. The whiteboard design session may need to be updated as well. Highly unlikely.

While deploying the ARM template, this error makes it unable to finish deployment:
{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VnetSubnetConflictWithIntendedPolicy",
"message": "Precondition failed.. (https://go.microsoft.com/fwlink/?linkid=871071)"
}
]
}
}

The PowerShell command from this link is not working.
I've tried to deploy this template 6 times, same error appears every time.

Lab currently broken, please remove lab documents from the repo until we can repair and refresh.

The Migrating SQL databases to Azure MCW is ready for QC and publishing.

Exercise 4 Integrate App Service with the virtual network After configurung the Vnet with Web Application, web app should load but in my case its not loading.

Difference is I am having SQL-Mi instance and Vnet Gateway in different RG and Web app is in different RG, we configured everything with same Vnet only ( Regions is same only RG are different )

Can you please check this ASAP, I can share lab environment details to quickly check this.

Thanks
Abhishek

Facing issue in exercise 2 task 5 not able to login in source sql server. getting the below issue

After adding the ApplicationIntent=ReadOnly value to the TailspinToysReadOnlyContect, read READONLY label is not visible on the website after refreshing, even after restarting the app service.

The connection string has been copied and pasted from the lab guide, replacing the server address, but the page on the website doesn't appear to update as expected.

WDS Updates:
Update SSRS content and add newer Power BI integration
Update references to the new Azure SQL branding.
Add SQL MI related security benefits to the customer conversation.

Lab Updates:
Test all tasks in the labs
Update screenshots
Update references to new Azure SQL branding
Investigate adding SQL accounts to initial automation script
Task 5: Create a service principal
Check to see if this task needs to be updated or can be automated further. Possibly use a managed identity.

In the deck WDS trainer presentation - Migrating SQL databases to Azure.pptx, there are multiple references to "Customer objections". The correct term should be "Customer objectives"

Hi ,

After updating the connection strings ( ReadOnly at the end) it should show Read_Only data but it is showing Read_Write data only.

Could you please check on this?

Thanks
Abhishek

I am not able to login using WorkShopUser account. i found that this is because SQL Server authentication mode windows only. and this is not changing from the Configure-sqlVM.ps1, I am able to login after enabled the Mixed Authentication mode for SQL Server.

i have added this query in powershell script.

$query = "USE [master]
GO
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'LoginMode', REG_DWORD, 2
GO"
Invoke-Sqlcmd $query -QueryTimeout 3600 -ServerInstance $ServerName

Restart-Service -Force MSSQLSERVER

WDS Updates:
Update SSRS content and add newer Power BI integration
Update references to the new Azure SQL branding.
Add SQL MI related security benefits to the customer conversation.

Lab Updates:
Test all tasks in the labs
Update screenshots
Update references to new Azure SQL branding
Investigate adding SQL accounts to initial automation script
Task 5: Create a service principal
Check to see if this task needs to be updated or can be automated further. Possibly use a managed identity.

In exercise 4 task2:-
I have followed all the steps but the web app is not getting loaded.

• subnet is connected with web app
• Connectionstring is also updated with the database strings.

Getting the following error page.

There is an issue which we are getting when saving the classifications data in Data Discovery & Classification in Exercise 5, Task2, Step 11
Below is the screen shot error when we are adding the recommended classifications and saving the classifications.

Could you please elaborate more on this ? Why Trial subscriptions will not work ?