Author: Vadim Osovitny (page 1 of 3)

New Azure Certification Paths

At Ignite Microsoft announced a new role-based certifications: Azure AdministratorAzure DeveloperAzure Solutions Architect, Azure DevOps Engineer; Microsoft 365 Modern Desktop Administrator and Enterprise Administrator. In fact, the exams for the Azure Administrator certification are now live, and the next two certifications Azure Developer and Azure Solutions Architect have exams in beta. The other three role-based certifications on this list will be launched before the end of the year.

Continue reading

532-533-535 Exams Retirement

Source: https://www.microsoft.com/en-us/learning/community-blog-post.aspx?BlogId=8&Id=375158

Azure fathers: Dave Cutler and Amitabh Srivastava

In 2006, Amitabh Srivastava was a corporate vice president in Microsoft’s Windows division, working on redefining the organization’s engineering processes.  Ozzie had recently been named the company’s chief software architect and the two had their first meeting one late afternoon in Building 34 on Microsoft’s campus.

Srivastava has always had a rule: If he’s in town, he never misses dinner at home with his family – or if he needs to, he tells his family he’ll be late.  That evening, Srivastava lost track of time.  He missed dinner and never called home to say he’d be late.  The one-hour meeting began at 4 p.m. and went until 8 p.m.

“By the end of that meeting, I was convinced software wouldn’t be shipped as it had been.  My personal realization was, ‘I’m working on the wrong thing,’” Srivastava recalled.

At the time, Srivastava’s office was across from Cutler’s, and the two often got to the office early.  Soon after the meeting with Ozzie, Srivastava recalls telling Cutler, “I don’t know what needs to be done, but I know there’s something changing dramatically and we’ve got to rethink our approach.”

After a few more weeks of discussions, Srivastava knew Microsoft needed to build an operating system for the cloud, and he identified his first task: Recruit Cutler.

“So I go to Dave and he says ‘I think I’m ready to retire,’” Srivastava said. “I said, ‘Dave, not quite. This is different.  This could change the world.’”

Cutler didn’t say yes to Srivastava, but he also didn’t say no.  “I had worked with Dave long enough to know that when he didn’t say no right away, that was a good sign.”

Srivastava developed a plan for Cutler and him to visit every team at Microsoft running a cloud service, from MSN and Hotmail to Xbox Live and the company’s cloud data centers.

The due diligence process took a few months as Cutler and Srivastava listened to the pain points and band-aid approaches teams had taken to keep their cloud services running.  After the tour, Cutler and Srivastava never had a formal discussion about him joining the team. Cutler was on board.

Two years later, on Oct. 27, 2008, Ozzie stood on stage at the company’s Professional Developer’s Conference in Los Angeles and announced a technology preview of Windows Azure (now Microsoft Azure).


At PDC 2008, Ray Ozzie announced a technology preview of Windows Azure (now Microsoft Azure).


Amitabh Srivastava on stage at PDC 2008, wearing the “Project Red Dog” sneakers that Cutler designed.

Original: https://news.microsoft.com/features/the-engineers-engineer-computer-industry-luminaries-salute-dave-cutlers-five-decade-long-quest-for-quality/ 

Windows Azure Pack (WAP) is not dead

Windows Azure Pack lifecycle was updated

It means that:

  1. Azure Pack is not dead, and it’s far from being dead.
  2. Azure Pack will continue to evolve until 2022 (6 years from now) and will be supported until 2027 (11 years from now).

Remember that Microsoft Azure Stack is not the new version of Windows Azure Pack (WAP). Azure Stack release in 2017 won’t kill WAP – they will co-exist together for a long time. Azure Stack and WAP have a different purpose – WAP is a great solution to build IaaS, and Azure Stack is a great platform to run Azure services in your datacenter. They are totally different inside and very different from the outside – WAP looks like a simplified old Azure Portal, while Azure Stack looks exactly like new Azure Portal. WAP is built on top of Windows Server and System Center and can run on a vast varieties of hardware, supported by Windows Server 2012R2/2016. Azure Stack architecture is inspired by Azure, uses Azure Resource Manager model and can run only on a specific supported hardware.

It’s great that Microsoft supports both approaches. Service providers can use WAP to build a great IaaS solution, using the hardware they like or already have. They can use Azure Stack to build a “little Azure” in their DCs.

What is Windows Azure Pack (WAP)?

Windows Azure Pack (WAP) is a collection of Windows Azure technologies, available to Microsoft customers at no additional cost for installation into your data center. It runs on top of Windows Server 2012 R2 and System Center 2012 R2 and, through the use of the Windows Azure technologies.

Services that are available out of the box with WAP:

  1. Virtual Machines (via System Center VMM integration)
  2. Websites (distributed, multi-tenant, highly available web hosting service)
  3. Database (via SQL Server and My SQL)
  4. Automation (via System Center Runbooks)

Resources:

  1. Step-By-Step: Installing Microsoft Azure Pack for Windows Server
  2. Windows Azure Pack – Infrastructure as a Service 

Azure AD B2C for ASP.NET Core Web Application

Azure Active Directory (Azure AD) B2C is an identity management service that enables you to customize and control how customers sign up, sign in, and manage their profiles when using your applications.

Learn how to set up identity management for the customers that use your ASP.NET Core Web Application:

Step 1: Create an Azure AD B2C tenant
Step 2: Register an application
Step 3: Create sign in & signup policy
Step 4: Add configuration details inside .NET app

Learn more:

  1. Azure Active Directory B2C Documentation
  2. https://github.com/Azure-Samples/active-directory-b2c-dotnetcore-webapp
  3. Getting Started with Azure AD B2C Built in Policies

Azure AD B2C: How to enable consumer logins and access management for your B2C apps

Azure Active Directory B2C

Azure Active Directory (Azure AD) B2C is an identity management service that enables you to customize and control how customers sign up, sign in, and manage their profiles when using your applications. This includes applications developed for iOS, Android, and .NET, among others. Azure AD B2C enables these actions while protecting the identities of your customers at the same time.

Resources:

  1. https://azure.microsoft.com/en-us/services/active-directory-b2c
  2. https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-overview

Azure AD, B2B, B2C

Azure AD

Azure Active Directory (in short  Azure AD) is a cloud identity provider service or Identity as a Service (IdaaS) provided by Microsoft. Its primary purpose is to provide authentication and authorization for applications in the cloud (SaaS apps).

Azure AD B2B

Now for Azure AD B2B (which of course stands for Business-to-Business). Is it a different version of Azure AD? No! It’s only one of its service features. It allows one organization to invite members from other organizations to share application access.

Azure AD B2C

Azure Active Directory (Azure AD) B2C: it is a separate service from Azure AD. Built on the same technology, but still… for different purposes. It’s  an identity management service that enables you to customize and control how customers sign up, sign in, and manage their profiles when using your applications. Also it’s built to allow anyone to sign up as a user in a service with their email or social media provider like Facebook, Google or LinkedIn.

Regions, availability zones, and fault domains

A region, is a geographical region on the planet, potentially multiple datacenters in close proximity, networked together. Those datacenters are sometimes called availability zones. An availability zone, has its own independent power and networking. It is set up to be an isolation boundary. If one availability zone goes down, the other continues working. The availability zones are typically connected to each other through very fast, private fiber-optic networks.

Within the availability zone, the VMs are deployed on machines, that are organized in racks. Each rack has its own router. The virtual machines on one single physical machine may run multiple containers.

When an incoming request comes to the endpoint, it is usually first delivered to a load balancer to route the traffic to an instance of a service. The goal is to run the code on different VMs that are not close to each other to reduce the chance of single point of failure. The unit of single point of failure is called a fault domain. With this hierarchy, when:

  • a region goes down, everything inside the region is down.
  • an availability zone goes down, everything inside the availability zone is lost.
  • a rack goes down, it is the PCs that are lost.
  • a PC goes down, it is the VMs on it that are lost.

 

Older posts