Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Security | Vulnerability Scans and Assessment » Register Devices to Intune and EntraID Using Company Portal

Register Devices to Intune and EntraID Using Company Portal

Posted on 09/11/202312/11/2023 Imoh Etuk By Imoh Etuk No Comments on Register Devices to Intune and EntraID Using Company Portal
How-to-Register-Devices-to-Microsoft-Intune-and-EntraID-Using-My-Company-Portal-

In this post, I share how to register devices to Intune and EntraID using the company portal. Microsoft Intune and Microsoft Entra ID (formerly Azure AD) offer organizations and individuals the ability to manage all their devices from one central place. In managing devices using Microsoft Intune and Entra ID. There are several methods one can use. These devices must be either joined or registered. Please see Domain Name System Protocol: Client Registration Issue, and Azure Active Directory integration with on-premise AD using PTA.

Company Portal is an app that lets you, as an employee of your company, securely access resources. Before an employee can use this app, they must be sure that their IT administrator has set up their work account.

Microsoft Intune can also be used to configure Windows LAPS Management. Considering Intune capabilities, you can also use it to carry out complete monitoring and reporting for Microsoft Defender Antivirus.

Also, you use Intune alongside GPO to modify Windows 11 taskbar. Microsoft Intune lets organizations securely manage identities, apps, and devices. On the other hand, Microsoft Entra ID is a one-stop shop for all things cloud-based identity and access management. To learn about ADK, MDT, SCCM, Intune Autopilot, and WSUS.

The question most people might want to ask at times is: Why implement an identity and access management solution and a device management solution? Well, while there seems to be no one-size-fits-all answer to this question, the bottom line is that organizations must secure their digital assets.

Let’s look at the differences between the Microsoft Entra device joined and the device registered to better understand how managing devices in Microsoft Entra ID and Intune works.

Microsoft Entra Device Joined vs Registered

When devices are joined to Microsoft Entra. It means that users have signed in using an organizational Microsoft Entra account. With this method, the device is owned by the organization. The device, when joined to the Microsoft Entra, will appear as “joined“. Authentication for Microsoft Entra-joined devices is done using Entra ID authentication.

It has support for Windows 10/11 (not Windows 10 Home). This means only Windows devices can be joined to Microsoft Entra AD. The device onboarding process is done through OOBE (out-of-box experience), bulk enrollment, and Windows Autopilot. Joined devices exist across on-premises and the cloud.

Microsoft Entra devices registered, on the other hand. They are devices owned by employees who are now registered with Entra ID and Intune. It has support for Bring Your Own Device (BYOD).

The authentication for the registered devices is done using a local account. It supports Windows, macOS, iOS, Android, and Ubuntu devices. Device registration can be done using Windows settings and the company portal app. All registered devices exist in the cloud.

Having understood the differences between the Microsoft Entra device joined and registered, let’s proceed to implement the Microsoft Entra device registered method using the company portal.

How to register Devices to Intune and EntraID using the Company Portal

To register devices with Microsoft Entra ID and Intune, follow the steps below:

Step 1: Download the company portal app by clicking on this link.

Install-Company-Portal-
Install the Company App

Wait for the installation to complete. Open the app in the next step.

Step 2: Click on the message similar to the one below to begin the setup.

Set-device-for-corporate-use
Setting up Device for Corporate Use

Step 3: Setup your device by adding your corporate account.

Add-corporate-account
Setting device

Step 4: Connect to work

In this step, you must connect your device to work before you can have access to company apps and resources. This means adding your corporate email.

Connect-account
Connect your device to work

Proceed to the organization’s sign-in page.

10-Taking-you-to-the-sign-in-page
Redirecting to the company’s sign-in page

Follow the prompt to sign in with your corporate email and password. Implement the MFA authentication, if any, and proceed.

Add-your-email-click-next

Enter your password to sign-in

Enter-password-sign-in

Enter the code

Verify-your-sign-in-with-MFA
Hang on while your device is being registered. 

On completion, click on “Got it” to return to the successful screen.

7- 0 wait while the device is being registered

Your device is being set up

8-Registration-complete

You will see a successful screen indicating that your device is now connected to work, as shown below.

Your-device-now-connected

Click Done to exit the screen.

9- Check-status-to-verify-it-connected

Device Registration Succeeded

From the above, click on Next to continue to the next page. This shows your device was successfully registered.

Status-Succeeded
Device Registration Succeeded

Step 5: Sign into your Microsoft Entra ID Admin dashboard to see the device. You can also access the device through the Azure Portal by clicking on Microsoft Entra ID > Devices > All Devices.

13-Device-now-on-Entra-ID
Microsoft Entra ID Registered Devices

You will notice under the Join device type that the status is shown as “Registered”.

Head over to the Intune Admin dashboard to verify that the device also appears there.

15-Device-managed-by-Intune
Intune Admin Center
You notice that on the Inune Admin Center. The device ownership is shown as "Personal",  which means the device is owned by an employee, which complies with the BYOD policies.

To check the enrollment state, click on the registered device name and then click on the “Enrollment” tab on the Intune Admin Center, as shown below:

14-Device-Enrollment-on-Intune
Device Enrollment Status on Intune

In conclusion, registering devices to Microsoft Entra ID and Intune provides organizations with enhanced security, streamlined management, an improved user experience, and cost efficiency, making it a valuable solution for modern workplace environments.

I hope you found the post on Register Devices to Intune and EntraID Using Company Portal useful. Please feel free to leave a comment below.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
AWS/Azure/OpenShift, Security | Vulnerability Scans and Assessment

Post navigation

Previous Post: How to update Gitlab-runners on Windows
Next Post: How does Key Rotation work in MBAM?

Related Posts

  • Feature image LSA
    How to configure additional LSA Protection Security | Vulnerability Scans and Assessment
  • Convert PEM to PPK 1
    Convert a PEM Key to a PPK Key on a Linux and Windows AWS/Azure/OpenShift
  • MFA
    Rolling out Multi-factor Authentication – Recommendations Security | Vulnerability Scans and Assessment
  • 5rgh65436
    New Windows 11 encryption features and security enhancements for Hybrid Work Security | Vulnerability Scans and Assessment
  • Trellix ePO Repair and reinstall
    Fix Trellix ePO DAT and Engine Packages missing Security | Vulnerability Scans and Assessment
  • Deploy static website to azure blog storage
    Deploy a Static Website to Azure Storage from VSCode AWS/Azure/OpenShift

More Related Articles

Feature image LSA How to configure additional LSA Protection Security | Vulnerability Scans and Assessment
Convert PEM to PPK 1 Convert a PEM Key to a PPK Key on a Linux and Windows AWS/Azure/OpenShift
MFA Rolling out Multi-factor Authentication – Recommendations Security | Vulnerability Scans and Assessment
5rgh65436 New Windows 11 encryption features and security enhancements for Hybrid Work Security | Vulnerability Scans and Assessment
Trellix ePO Repair and reinstall Fix Trellix ePO DAT and Engine Packages missing Security | Vulnerability Scans and Assessment
Deploy static website to azure blog storage Deploy a Static Website to Azure Storage from VSCode AWS/Azure/OpenShift

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • Task Scheduler Greyed Out
    How to fix Task Scheduler Service Greyed Out in Service MMC Windows
  • RDS Architecture
    The following servers in this deployment are not part of the deployment Pool: Create an RDS Session Host and Collection Windows Server
  • control panel
    Enable or Disable Control Panel and Windows Settings App Windows
  • Configure NFS on Windows Server
    How to install NFS Server on Windows Server Windows Server
  • savds
    VM is not accessible: Fix Taking ownership of a VM failed Virtualization
  • jmeterlogo 3
    Install and conduct performance testing using Apache JMeter on your Web App Configuration Management Tool
  • Upgrade for Veeam ONE
    How to upgrade Veeam ONE to v12.1 Backup
  • ansible logo600 591x296 1
    Ansible_user=UNREACHABLE {Failed to connect to the host via SSH: SSH: Could not resolve hostname (Name or service not known, unreachable true) Configuration Management Tool

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,813 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.