Cannot deploy Defender for Business to macOS computer

Alex D 20 Reputation points

I have been trying to deploy Defender for Business to a macOS computer, but each time I get an error "No License Found. Looks like your organization does not have a license for Microsoft 365 Enterprise subscription".

The macOS computer is successfully joined to Intune. I have tried two methods to deploy Defender for Business: by creating a Defender app in Intune and installing it using Company Portal on the Mac; and by downloading and running the installer. In both cases, the installation runs through to the end successfully, but on clicking on the Defender icon on the Mac, I get the above error.

Strictly the error is correct, we do not have an Enterprise subscription, we are running Microsoft 365 Business Premium. Business Premium includes Defender for Business. Allegedly Defender for Business is compatible with Intune, but I am at a loss to see how to get it working.

Any ideas?


Microsoft Intune MacOs
Microsoft Intune MacOs
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.MacOs: A family of Apple operating systems for the Apple Mac line of computers.
73 questions
0 comments No comments
{count} votes

Accepted answer
  1. Lu Dai-MSFT 28,366 Reputation points

    @Alex D Thanks for posting in our Q&A.

    Based on my research, I find that this error message is recorded in the official article. Please refer to the following article:

    It is suggested to update Microsoft Defender for Endpoint on macOS to the lastest version. Then try to Follow the instructions.

    Hope it will help.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    2 people found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Alex D 20 Reputation points

    @Lu Dai-MSFT

    Thank you for responding quickly. My problem was that I had not run the client configuration script, Once I did that, everything was OK.