Update pricing-features-table.yml #20609
Conversation
Moved description and moreInfoURL info for consolidated features.
Add "coming soon" to application management Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
- Consolidated "Native macOS update reminders" with "Enforce operating system (OS) updates"
|
Thanks @noahtalerman. I addressed your comments and re-requested your review. |
…enrollment" Renamed "User-initiated enrollment of macOS computers" to "Aut
| @@ -649,7 +653,8 @@ | |||
| pricingTableCategories: [Device management] | |||
| waysToUse: | |||
| - description: Send software vulnerability emails to end users to encourage self-remediation. | |||
| - industryName: User-initiated enrollment of macOS computers | |||
| - industryName: Automated enrollment | |||
There was a problem hiding this comment.
@noahtalerman, I missed this one. I renamed and added a tooltip. “User-initiated enrollment” is a deprecated Jamf feature that we shouldn’t use in our language. We could add “Account-driven user enrollment” (which I think "User-initiated..." is referring to) as a separate line item, but I don’t think it’s needed at this point. It might come up with iOS, though.
cc @nonpunctual
There was a problem hiding this comment.
Hey @mike-j-thomas I think what we mean by "User-initiated enrollment" is what folks think of as "BYOD enrollment" or "Manual enrollment."
"Automated enrollment" is synonymous with "Zero-touch enrollment"
What Jamf calls "User-initiated enrollment (deprecated)" is enrolling a specific user on a macOS host (instead of the host itself). Apple has released "Account-driven enrollment" to handle this workflow. Fleet today supports neither because it's not a common use case in the enterprise.
There was a problem hiding this comment.
I committed the change from "Automated enrollment" to "BYOD enrollment" and approved the PR, so I'm not blocking the merge if the changes look good to you.
As part of our Q2 OKR to list features that Mac Admins care about first, we have also renamed features to make them easier to understand.
Style guide for the naming convention:
More context for this PR: #20191. Once these name changes are approved, we will follow up with the re-ordering.