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:
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.
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.
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.
Availability Zones is a high-availability offering that protects your applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there’s a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone-redundant services replicate your applications and data across Availability Zones to protect from single-points-of-failure.
Azure services that support Availability Zones fall into two categories:
Zonal services – you pin the resource to a specific zone (for example, virtual machines, managed disks, IP addresses), or
Zone-redundant services – platform replicates automatically across zones (for example, zone-redundant storage, SQL Database).
To achieve comprehensive business continuity on Azure, build your application architecture using the combination of Availability Zones with Azure region pairs. You can synchronously replicate your applications and data using Availability Zones within an Azure region for high-availability and asynchronously replicate across Azure regions for disaster recovery protection.
A geography is a discrete market, typically containing two or more regions, that preserves data residency and compliance boundaries. Geographies allow customers with specific data-residency and compliance needs to keep their data and applications close. Geographies are fault-tolerant to withstand complete region failure through their connection to Microsoft dedicated high-capacity networking infrastructure. Geos examples: US, Europe, Asia Pacific, Japan, Brazil, Australia, China. Learn more >
A region is a set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. With more global regions than any other cloud provider, Azure gives customers the flexibility to deploy applications where they need to. Azure is generally available in 40 regions around the world, with plans announced for 10 additional regions
Availability Zones are physically separate locations within an Azure region. Each Availability Zone is made up of one or more datacenters equipped with independent power, cooling, and networking. Availability Zones allow customers to run mission-critical applications with high availability and low-latency replication.