How To Work With Microsoft Graph Explorer

Microsoft Graph

Graph Explorer is a tool that is mainly aimed at developers, but anyone can use it to learn more about the Graph APIs and how the queries should be constructed. In the previous article, we saw how to install and work with the Graph API from PowerShell. In this article, we will have a look at how to use Graph Explorer, which is more visual.

You can launch graph explorer by navigating to Below is how it looks.

MS Graph Landing

You have the sample queries to help you get started on the left hand side, the middle top bar shows the specific entity and API modules we are querying. The output from the commands executed are shown in the ‘Response Preview’ tab. You do not have to login to your tenant to get started, as the sample queries are backed by a sample tenant.

For example, running (which is there by default) will show details about Megan Bowen, who is listed an auditor.

Megan Bowen MS Graph

If you now sign into your tenant with your M365 credentials using the button at the end (above the ‘run query’ button), you will be prompted to accept the permissions required.

Sign into MS Graph
User consent

You do not have to ‘consent on behalf of the organization’ to run any query which is personal to you (like obtaining your profile info, querying for your photo in Azure AD etc). If you are an administrator, you can check the consent box and accept the permissions on behalf of the organization, so that other users won’t be asked to do the same.

Sure enough, it will return information about you which is in your Azure AD tenant. Any user (without any admin rights) can perform this action or any action that you are allowed to do normally (creating a Microsoft Team for example).

Query profile MS Graph 1

You can run the sample query on the left hand side to display your photo (if you have one in the cloud). Click on the GET button against ‘my photo’ and the query will be updated. Clicking the ‘run query’ button will show your photo in the response pane.

Get Photo MS Graph

You get the idea, you can try the other queries listed like getting your manager info, your mail, items in your drive etc. This is where the power of Graph API comes in. You can query Azure AD, Exchange Online, SharePoint etc by connecting to a single endpoint. Previously, we had to connect to each workload separately to get the response. And this was proving hard when you wanted to run a script that queries data from various workloads to bring it into a single output file.

If you try running the query for ‘my mail’, you may be welcomed with an error message. This is because we don’t have the permission to the scope ( yet.

Reading email MS Graph fails

But we can sort the permissions ourselves by clicking on the ‘modify permissions’ tab, selecting the permission we need and consenting. Notice that there is a cross mark against the ‘admin consent’ column, which means that any user can acquire this permission without getting a consent from the admin.

Modify permissions MS Graph

Click on the consent button against and agree to the new set of permissions.

Mail consent pop up

Run the query again. Sure enough, the email information is displayed in the response tab.

Email response MS Graph

You might be thinking as to how this Graph Explorer is bringing the information back and where these consents are getting processed. Let me explain how it works.

The Microsoft Graph Explorer is configured as an enterprise application in your tenant out of the box. If you navigate to ‘Enterprise Applications’ & search for Graph, it will come up.

Graph Explorer Enterprise App

Click on the Graph Explorer app and navigate to the ‘permissions’ tab -> User Consent. This area will list all the consents that the users in your tenant have made.

Graph Explorer Permissions

As an administrator, you can consent permissions on behalf of the organizations as well.

Admin grant consent MS Graph

In short, Graph Explorer is an enterprise application which is guarded by Azure AD from an authentication standpoint. Once you are authenticated, you can access any workload & get results if you have the permissions.

To summarize, we have learned

  • What Graph Explorer is.
  • How to navigate the tool.
  • How to run sample queries.
  • How to run queries against your own tenant.
  • How to modify permissions and consent and
  • A tour of the Graph Explorer app in Azure AD.

Do let me know if you have any questions in the comment section below.

Other Popular Articles

How To Install Microsoft Graph Beta Module

Error – Select-MgProfile is not recognized as the name of a cmdlet, function or script file

Microsoft Graph

Build Microsoft Graph Scripts With Azure AD App – Detailed Guide

Microsoft Graph

How To Install & Work With Microsoft Graph

Leave a Comment

Disable Windows Copilot Using Intune

Windows Copilot is Microsoft’s take on making life easier for Windows users using the power of AI. This article explains how to disable the feature using Intune, if your organization is not ready yet to walk into the AI world.

Disable Windows Copilot Using Intune

We need to create a Configuration Profile for Windows devices in the Intune portal to disable Windows Copilot. Below are the steps that we need to create the profile.

Launch the Intune Portal and login as a Global Admin or Intune Admin.

Navigate to Devices -> Windows -> Configuration Profiles.

Windows Configuration Profile Intune

Click on Create -> New Policy.

Select Windows 10 & later as the platform and Settings Catalog as the profile type & click on the Create button.

Settings Catalog Intune CoPilot

Give the policy a meaningful name & description and click Next.

Policy Name Disable CoPilot

Within the configuration settings, click on the Add Settings option.

Add Settings Disable CoPilot

Search for ‘copilot’, Windows AI will come up as the category. Click on Windows AI and the Turn off Copilot in Windows (User) setting will come up. Check the box and click Next.

Turn off CoPilot Setting Intune
Turn off CoPilot Setting Intune Summary 1

Specify scope tags if required and click Next.

Select tags CoPilot Intune

Select who this policy should apply to in the Assignments section. I have selected to add all users. If you want to test the setting, you can create a test group and select that group here.

Similarly, you can also exclude certain group from disabling AI (say IT team) if required.

Add all users disable copilot intune

A summary of selected settings will be displayed. Click on the Create button to setup the policy to disable Windows Copilot.

Create configuration policy disable CoPilot Intune 1

Wait for the replication to complete in the cloud backend and login to your machine. Your chatty Copilot should now be disabled.

Disable Windows Copilot On Windows 11 Pro

Follow the steps below to disable Copilot on a personal Windows 11 Pro machine (say your own laptop).

Search for ‘group’ in Windows 11 and click on Edit Group Policy option.

Group Policy Windows 11 Disable Copilot

Navigate to User Configuration -> Administrative Templates -> Windows Components -> Windows Copilot.

Windows Copilot GPO setting

Double click on Turn off Windows Copilot setting on the right pane.

Select Enabled and click OK.

Turn off copilot gpo Windows 11 Pro 1

Close the Group Policy Editor. This will disable Windows Copilot on a Windows 11 Pro machine.


We have learned to disable Windows Copilot using Intune and Group Policy on Windows 11 machines.

Please let me know if you have any questions in the comments section.

Promote Windows Server 2025 To Domain Controller

Domain controllers are the backbone of any Active Directory domains in the Microsoft world. Any Windows server can be promoted to be a domain controller. In this article, we will go through the steps of promoting a Windows 2025 Server to be a domain controller.

Windows Server 2025

The latest version of the server operating system has been named Windows Server 2025. You can start with a 2025 Server & create an AD domain or you can promote a member server that is already a part of a domain.

The Windows Server 2025 needs to be installed on a machine before it can be promoted to be a domain controller.

Promote Windows Server 2025 To Domain Controller

If you have been working with Windows servers long enough, everything starts with the Server Manager app. Promoting a server to a domain controller is no different.

Launch ‘Server Manager’ & click on Add roles and features.

Windows 2025 Server Manager

You land on the summary page that explains what is required to run this wizard successfully. Click Next.

Windows Server 2025 Add Remove Roles

Select Role-based or Feature-based installation and click Next.

Windows Server 2025 Role Based Install

Select the server that needs to be promoted and click Next.

Windows Server 2025 Destination Server

Select Active Directory Domain Services (second option) and click on Add Features.

Windows Server 2025 AD Domain Services

Go with the default options for features that need to be installed.

Windows Server 2025 AD Domain Services Features

A summary of AD DS pops up next, click next to continue.

Windows Server 2025 AD DS

Select Restart the server automatically if required and click Install.

Windows Server 2025 AD Restart Server

You get to keep an eye on the progress of the installation.

Windows Server 2025 AD Install Progress

Once the role has been installed, you will find an exclamation mark on the top right corner of the Server Manager. Click on that and select Promote this server to be a domain controller.

Windows Server 2025 AD Install Continue

You get an error straight away (which you have never seen before) – Error determining whether the target server is already a domain controller. Role change is in progress or this computer needs a restart.

Windows Server 2025 Domain Controller Setup Error

We never needed to restart the server after installing the role in the DC promotion process. Given that it is an insider build of Server 2025, I am hoping that this will get fixed before the public release.

Restart the server, launch Server Manager and click on the Promote this server to be a domain controller option again.

Windows Server 2025 AD Install Continue 1

I am setting up a brand new AD forest and hence I select the third option (Add a new forest) and enter my root domain name.

Windows Server 2025 Add a forest

Next window brings the option to set your forest & domain functional level and the DSRM password. In the insider build, it shows what looks like a variable (the Windows server version on which the you are working).

Windows Server 2025 Forest Functional Level

You can leave the default options in the DNS options wizard and click next.

Windows Server 2025 DNS Options

Enter the netbios name of the domain in the next window and click next.

Windows Server 2025 Netbios Domain Name

You can stick with the default paths for the AD database, log & sysvol folder or pick a location of your choice.

Windows Server 2025 AD Paths

Review the selections that you have made so far and click next.

Windows Server 2025 Options Review

Wait for the green check mark on the prerequisites page and click next.

Windows Server 2025 Pre reqs Check

Click Install in the final window & wait for the magic to happen. Once the machine gets restarted (which it will do automatically), you will have a brand new domain controller based on Windows Server 2025.

Windows Server 2025 AD Snap In


Promoting a Server 2025 to a domain controller follows pretty much the same steps as previous operating systems. The Insider build has few errors that needs to be fixed, but hey, it is an insider build!

Please let me know if you have any questions in the comments section.

Install Windows Server 2025 – Full Guide

Microsoft has released an insider preview of it’s next server operating system named Windows Server 2025. We will have a look at the installation steps involved in setting up a 2025 server.

Windows Server 2025

Microsoft has gone with the same look and feel of Windows 11 operating system in it’s current server operating system – Windows Server 2025. As the product is in insider preview, there might be slight changes before it hits the public shelves.

It is refreshing to see a ‘modern’ feel in the installation process of a server operating system. Gone are the days where the installation of a consumer based OS felt much better compared to it’s server counterpart.

Installing Windows Server 2025

Let’s take a look at the steps involved in setting up a Windows Server 2025 machine. First step is to download the ISO from the Windows Insider portal.

Next step is to boot the virtual / physical machine from the ISO which will kick off the installation of Server 2025.

First option to select is the language settings. Pick the one based which relates to you and click next.

Windows Server 2025 language settings

Select the keyboard settings in the next screen and click next.

Windows Server 2025 keyboard

You get the option to select whether you want to Install Windows Server or Repair the installation. The bottom left corner also has the option to go to the previous version of setup.

Windows Server 2025 setup option

You are asked to enter the product key, which is available in the Windows Insider portal.

Windows Server 2025 product key

Next option to choose is the type of image you want to install – Windows 2025 core or full blown desktop experience.

Windows Server 2025 Desktop

You need to agree to the licensing terms to move forward in the next step.

Windows Server 2025 Agreement License

Select the partition on which the server OS should be installed and click next. You also have the option to slice the partitions the way you see fit in the same screen.

Windows Server 2025 Disk Partitions

The Ready to Install window comes up, click the install button.

Windows Server 2025 Install 1

Installation of Server 2025 is underway and you get to see the progress.

Windows Server 2025 Install Progress

Once the installation is complete, you need to enter an administrator password of your choice to finalize the setup.

Windows Server 2025 Password

And there you go! You see a Windows 11 login screen staring at you ;-)

Windows Server 2025 Login Screen

After logging in, you get to set the options around sending diagnostic data to Microsoft, which I always set as ‘required only’.

Windows Server 2025 Diagnostic Data

The Windows Server 2025 desktop looks similar, doesn’t it? ;-)

Windows Server 2025 Desktop Feel scaled

Now that the server is up and running, you can promote it to be a domain controller.


The Windows Server 2025 has the same look and feel as a Windows 11 operating system. The installation options also provide that modern ‘feel’ and makes it a bit soothing to the eyes!

Please let me know if you have any questions in the comments section.