Skip to main content

Azure Active Directory B2B

This is an extension of Azure Active Directory Service.

Simplest way to think is if the organization wants to collaborate with another organization by sharing their applications, then the IT has to think of a way to provide access to the users.
Also policies have to be set to remove the access and restrictions around the access to applications.

Azure AD B2B does this for you.
Users will be sent a invite using which they can use their own preferred account to access the applications.
Users can use their social networking account to access the applications, while Azure AD strong policies take care of the applications that can be accessed by users.
If the organizations want to use their corporate accounts, then the users need to create a password first and use their corporate account. As per the Microsoft in the future they will collaborate for SSO so that users do not need to create new passwords.
Azure AD B2B will also allow users to be added to administrator groups.

What is the difference between Azure AD, B2B and B2C?
Azure AD
Azure AD is a identity as a service (IdaaS) for authentication and authorization of cloud applications.
Organization users login to your domain, dedicated for your organization.
Users on premise are continuously synchronized to Azure AD

Azure AD B2B
This is an extension of Azure AD. 
Users from different organizations will be provided access to your organization applications.
Members are invited to access the applications.
Cross organization collaboration

Azure AD B2C
This is similar to AD but has different functionality.
Consumer are allowed to sign-up and sign-in to your applications.
Used widely for mobile and web apps that have to be open to wider users not restricted to corporates.
Eg. You have created a new Skill app, you want to extend it to all users.
End users want to know their Skill, so they sign up for your app and use it.




Labels:

Comments

Post a Comment

Popular posts from this blog

Kubernetes: 6. Imperative Commands

Imperative commands are useful in quickly creating the resources on Kubernetes kubectl --dry-run -> When created with this option, Kubernetes just validates the definition and does not actually create the resource -o=yaml -> Gets the output in YAML format kubectl run nginx-pod --image=nginx:alpine  -> Create a pod with name nginx-pod and image nginx:alpine kubectl run httpd --image=httpd:alpine  -> By default, run implies run-a-pod kubectl run redis --image=redis:alpine --labels=tier=db  -> Create a pod with name redis and image redis:alpine and labels set to tier=db kubectl run custom-nginx --image=nginx --port=8080  -> Create a pod with name custom-nginx and image nginx to run on port 8080 kubectl expose pod redis --port=6379 --name=redis-service  -> Create a service with name redis-service to expose pod named redis on service-port 6379 kubectl create deployment webapp --image=kodekloud/webapp-color --replicas=3  -> Create a depl...
Post a Comment
Read more

Kubernetes: 21. Secrets

Passwords In the webapps we store the properties file for storing and retrieving the data required by application But we never store the application passwords, truststore, keystore passwords etc here We might store them in an encrypted format, but storing them as plain text is not the correct way In Kubernetes we store these sensitive information in Secrets https://medium.com/avmconsulting-blog/secrets-management-in-kubernetes-378cbf8171d0 Secrets Secrets are used to store the sensitive information They are similar to ConfigMaps, except that they are stored in hashed or encoded format Note that they are only encoded (using base64) but are not encrypted So secrets are a safe option to store sensitive information but infact they are not the safest option As such secret objects should be not checked into source code tools, its best to store them encrypted at REST in ETCD Again as in ConfigMaps, we have to create the secrets object first and then inject them into the pods There are 2 ways ...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more