Introducing the Simeon Resource Center!
Simeon is pleased to introduce the new Resource Center! The Resource Center is a central hub for all things Simeon Cloud, including submitting feature requests, accessing our product manual, opening support tickets, and sharing feedback with our Product Team.
A lot is going on in this little widget, so to help you get started, let's break down each section of the Resource Center.
CoreVoice:
CoreVoice allows the Simeon community to submit feature requests and ideas for enhancements, suggest new configurations to be supported, track your existing requests, vote on other user’s requests, provide feedback and comments on requests, and more! To submit a request, click the Resource Center icon in the top right > CoreVoice > Make a Suggestion. Want to see your existing requests? You will find these under the My Priorities section of CoreVoice.
Finally, to see what other users are requesting and vote or comment, navigate to the Suggested by Others section. Here you can vote for the features you think are most important to be added to Simeon, or to indicate that you do not like or want that feature. This feedback is actively reviewed by our product team and will be used to determine which features are selected for inclusion.
As a reminder, all feedback submitted through CoreVoice will be prioritized based on various indicators including feasibility, development time, and community demand. Feature requests are not guaranteed to be implemented!
Knowledge Resources:
The Knowledge Resources section of the Resource Center centralizes Simeon Cloud documentation and support resources. Here, you can find our Simeon Product Manual to guide new and existing users through key areas of Simeon. The Simeon Product Manual will first address installing tenants via the Install page, with Reconcile, Sync, and other areas of the app coming soon.
If you are experiencing an issue that requires assistance from our support team, you can open a support ticket directly from the Support link within Knowledge Resources. As always, support tickets can also be opened via email at support@simeoncloud.com.
Share Your Feedback:
Share your Feedback allows Simeon users to share any feedback or relevant experiences and barriers they have while using Simeon. This includes the ability to give us a rating, leave a message to our Product team, or book a 30-minute session with a member of our Product team to discuss any feedback you think is important. Please note that Share your Feedback is not a channel for support or for submitting feature requests!
Product Updates
The next version of Simeon Cloud is here! Simeon is pleased to announce that the rollout of the next major version of our Simeon Cloud software has begun! We have been working tirelessly to update our codebase to provide across-the-board efficiency gains, improve Sync performance, and introduce new features.
For an overview of what changes can be expected with the launch of this latest version, including a list of prerequisites and recommendations, please see our latest guide. We have already begun updating clients to this latest version and will continue to update more clients each week. If you have any questions or concerns regarding this update, please let us know by reaching out to support@simeoncloud.com.
A new workflow for removing tenants
When installing a tenant onto Simeon, certain resources may be created in the tenant to enable Simeon to function. Depending on what is selected at install time, this can include a service principal used for tenant authentication and configuration management or a service account for tenant authentication.
When removing tenants, we now prompt users if they would like to authenticate into the tenant to remove these resources. This process requires authentication as a Global Administrator in the tenant being removed.
If you would prefer not to remove these resources, or you would prefer not to authenticate into the tenant, you can select ‘No’ when prompted. This will remove the tenant resources from Simeon and Azure DevOps. Simeon resources in the tenant can be manually removed if desired.
Fixes and Improvements. The Simeon team is always hard at work for you!
[Fix] Addressed an issue where tenants could pend approval to add or remove a SharePoint site unexpectedly
[Fix] Prevented an issue deploying MSGraph/Domains when the configuration contains the isInitial property
[Fix] WindowsAutopilotDeploymentProfiles could fail to deploy in some cases
[Fix] Addressed an issue Syncing Device Configuration Profiles when Platform, PolicyType, or CreationSource was set
[Fix] Resolved an issue where deployments from the CIS Baseline could fail due to a missing localAdmins property
[Fix] Some Syncs could fail to set CreationSource for Device Configuration Policies
[Fix] Prevented an issue with Organization Configuration that caused Syncs to fail on export
[Fix] Improved handling when deploying Security and Compliance Labels
[Fix] Addressed an issue where creating Security Groups with duplicate mailNickNames would fail
[Fix] Resolved an issue when deploying Consent Policy Settings with EnableGroupSpecificConsent enabled
[Fix] Resolved a circular reference for Intune Applications that could cause some Syncs to timeout
[Fix] Prevented an issue where removing a tenant from the install page could fail
[Fix] Ensured that Simeon Baseline configurations are successfully deployed for clients on the next version of Simeon
[Fix] Deploying Device Configurations could error due to unresolved references
[Fix] Improve handling for deploying Device Compliance Policies with a block scheduled action parameter
[Fix] Improved handling of Transport Rule RMS templates to ensure these configurations deploy successfully
[Fix] Prevented an issue where some Summary Emails could show incomplete data for some tenants
[Fix] For clients on the next version of Simeon, the CIS Baseline has been appropriately named on Reconcile
[Fix] Some tenants could unexpectedly pend approval to remove a property of the Simeon Cloud Sync service principal
[Fix] Addressed an issue with DLP Compliance Rules where the AdvancedRule property contains a different structure between baseline and downstream tenants
[Fix] Ensure proper handling of unauthorized errors when the Sync writes changes to the tenant repository
[Fix] Resolved an issue deploying Device Enrollment Configurations due to the PlatformType being updated
[Fix] Improve support for deploying configurations when the baseline tenant is missing a necessary license
Thanks for Reading
Let us know how we can improve these updates and our platform by emailing us.
Thank You,
Team Simeon