Data Tips & Tricks

 Is there a way to read Azure Active directory Group (Service or Microsoft 365) programmatically  There are different ways to do it one of them is using AAD App  let's see with the following example:  Pre-requisite: Create an AAD App  Get the AAD Group Member Reader & User Read All permission through Microsoft Graph (application permission)  Create a client secret (we'll use this to access your AAD Group information in the context of AAD App) Create a CSharp project (detail mentioned below) Create and AAD App with AAD GroupMember read & user read all permission  Step-1: Create an aad app: Login to azure porta => Azure Active Directory => App registration => create new app   Step-2. Once AAD App is created (e.g.: AADGroupReader)        Open it.    Go to it's API Permissions ...

 Azure Active Directory (AAD) Group can be helpful in multiple places to do authentication & authorization for Azure PaaS application. Currently, there are two types of AAD Group Service (group): Used to manage computer and user access for a group of users. It can have users, group, device or another service principal as it's member and users. It can only have a service principal as it's the owner.  Microsoft 365 (group): Used to give members access to shared email-box, files, calendar and more.. It can have only users as it's a member. It's can be users or service principal both.  Let's see how to create AAD group (e.g. Microsoft 365 group):  Step-1: Login to your Azure portal ( https://portal.azure.com/ )  and go to Active Directory Group Step-2: Select the group and click on Add new group Step-3: Fill the required entries in New group form .  Select the group type Enter the group name.  Enter the description.  Click on Create button Step-4...

To manage the user's roles we use Service Account on OnPrem/IaaS servers. We can use this service account on our SQL Server and accordingly manage users' permissions for the users who are part of this service account. Suppose we have an Azure SQL and we want to manage set-of-users permission shall we create each-and-every users' user profile in Azure SQL and set the permissions accordingly. Obviously, we will not .  If we've anything like Service Account (or Group) on Azure we could create the user of this GROUP on Azure SQL and set its permission/role. Here comes the Azure Active Directory Group to help us.  In case if our organization has some scheduled tasks to sync Active Directory (service account) to Azure Active Directory (AAD group), already in place, there will be some delay when we add a user to the Service account and get reflected in the AAD Group. If we have a requirement that as soon as we add a user to our group we wan...

When we try to migrate our IaaS SQL to Azure SQL along with other code changes & refactoring, one of the most prominent things that come into the picture is Authentication through a client application (web app or windows form, excel-add-ins...). With IaaS/OnPrem SQL we could use Windows Authentication to let your client application interact with the SQL server with the user's context. But to Azure SQL we can't do the Windows Authentication and also we should avoid SQL-based login (user/password).  To login to Azure SQL, it's always preferable to use Azure Active Directory-based authentication (integrated flow, MFA, or AAD based password). Now the problem comes how to achieve this with your client application.  The solution to this problem statement is, u se AAD app with delegated permission to access the users' claim [email, sid] in access token & configure it based on your client (e.g. windows form, web application) Here are ...