VScope currently supports both Jamf Cloud and Jamf On-prem. Combined with the information from your Active Directory you can gain a deep understanding of your assets. If you think I skipped a step or didn't explain something clearly please let me know and I'll take a look.Integrating Jamf Pro with vScope allows you to view Computers, Local Users, Physical Disks and File Systems in vScope.
Note: This is how I accomplished this, it may not work for your environment. Requires Authentication: Enter the credentials of the service account you’ve created in M365.Sender Email Address: Enter the mailing address you want mail to be sent from.Step 3: Navigate to System Settings > SMTP Server Step 2: Select the Settings cog in the top right Step 1: Sign into your Jamf Cloud Instance Step 5: Select the Distribution List > Settings > Manage Delegates > Edit Delegates > Add a delegate > Add the service account you created and choose the “send on behalf” option. Step 4: Navigate to Recipients > Groups > Distribution List and locate the Distribution List you want to target. Step 3: Navigate to Exchange Online Admin Center from M365 Admin Center. In the User settings > Mail > Mail Apps > verify that Authenticated SMTP is enabled.
Jamf pro server license#
Assign a license that will provide this service account a mailbox.I added Exchange Admin as Administrator credentials to this service account. Step 2: Users > Active Users > Add a User It wasn't until after enabling the service account (account being authenticated in Jamf SMTP) to send as the distribution list that I was targeting mail was finally delivered.īelow is the configuration / solution which allowed for mail to be delivered successfully from Jamf Pro to our M365 Server using a service account without MFA. The "SendAsDenied" stuck out to me and I remembered in Exchange that you could configure an account to "Send As". .SMTPSendFailedException: SendAsDenied.Server log Error generated from authenticating with a service account created in M365 with no MFA enabled. I made exceptions with my user for MFA and I attempted trying to configure an "App Password" which doesn't seem to exist anymore? Or at least was not available within my users account settings for some reason. With the error above I messed around in Azure quite a bit and got no where. : Authentication unsuccessful, the request did not meet the criteria to be authenticated successfully.Server Log Error generated from an account with MFA enabled: Lets look at a couple server logs I was experiencing first.
It wasn't until after creating a service account without MFA applied it(account being authenticated in Jamf SMTP) and enabling "Send As" and "Send on behalf" in the distribution list by adding the service account to the delegates list that mail was delivered.
Our environment has MFA enabled and I was continuously fighting with both Jamf/Azure to figure out a workaround to the authentication errors I was seeing in the Jamf Server Logs. We have a distribution list that our Operations team are all apart of and wanted to receive email notifications from Jamf for a variety of reasons. I was really struggling to configure SMTP with M365.
0 kommentar(er)
