Tools, templates and assessments for the Adopt phase of CAF (Microsoft Cloud Adoption Framework)

Microsoft is offering an excellent framework to support cloud migration and adoption process –Microsoft Cloud Adoption Framework (CAF)

The framework defined an iterative process with the following phases:

Define Strategy
Plan
Ready
Adopt
Govern
Manage

For each of them, Cloud Adoption Framework (CAF) provides us a list of templates, tools, and assessment mechanisms that can help us to improve the adoption and migration process. Let's take a look at the ones for Adopt.

Strategic Migration Assessment and Readiness Tool

Location: https://docs.microsoft.com/ro-ro/assessments/?mode=pre-assessment&session=1e9bea1e-6e2a-46f0-bf60-897e0424b5e2

When you want to adopt cloud you need to be aware of all the dimensions that are impacted by the migration. This tool allows you to do an assessment of where you are in under 10 minutes and identify the dimensions that need to be improved to be able to achieve the adoption in a SMART way.

The covered dimensions are:

Business strategy
Partner support
Discovery & Assessment
Business case
Migration Plan
Technical Skilling
Landing Zone
Migration Execution
Governance
Management

For each dimension, you get a score and where needed a list of resources that can be used to do the improvements.

Azure migration guide overview

Location: https://ms.portal.azure.com/#blade/Microsoft_Azure_Resources/QuickstartPlaybookBlade/guideId/migration-setup

This guide is used during the Adopt phase to ensure that we cover all the steps from the process. For each step, we have the full list of steps, tools, and best practices that need to be taken into account, covering:

Assess
Deploy
Cost control
Release

Azure innovation guide overview

Location: https://ms.portal.azure.com/#blade/Microsoft_Azure_Resources/QuickstartPlaybookBlade/guideId/innovation-setup

The last tool that we have available for the Adopt phase is Azure Innovation Guide Overview. The guide supports us to improve the way how we drive adoption, build solutions, and engage with customers.

A list of services and tools are provided that helps us to:

Manage customer feedback: Set up tools and processes to manage the build-measure-learn feedback loop by using GitHub and Azure DevOps.
Democratize data: Data alone might be enough to drive innovative solutions to your customers. Deploy common data options in Azure.
Engage via applications: Some innovation requires an engaging experience. Use cloud-native application platforms to create engaging experiences.
Empower adoption: Invention is great, but a plan to reduce friction is needed to empower and scale adoption. Deploy a foundation for CI/CD, DevOps, and other adoption enablers.
Interact through devices: Create ambient experiences to bring your applications and data closer to the customers' point of need. IoT, mixed reality, and mobile experiences are easier with Azure.
Predict and influence: Find patterns in data. Put those patterns to work to predict and influence customer behaviors by using Azure-based predictive analytics tools.

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Cloud as a Story - Vunvulea Radu

Search This Blog