A white background with bright pink and bright blue hazy, organic shapes that are gradient

Specify which group can approve Syncs when installing a tenant!

January 8, 2024

If you use Simeon, you understand the importance of following best practices to secure your M365 environments. It is also important to secure your Simeon environment through correct user access and permissions.  With Simeon, you can set custom user access and achieve full RBAC for your environment. To help you get started, we have developed a guide with common permission scenarios. You can find this guide here.

‍

To make this process easier than ever, we are introducing the ability to select an approval group when installing a tenant! This approval group will allow you to specify which users can approve a Sync and deploy configuration changes to your tenants. To do this, navigate to Install > expand Advanced Settings >  select an approval group.


Platform Updates:

  • Simeon recently released an update that requires you to approve a change to Service Principal Authentication for all tenants. To ensure you receive the latest Simeon updates and to continue to Sync without issue, you must approve all tenants pending approval for this change as soon as possible. For information about this change, including what action you need to take, please see our FAQ here. If you have any questions, please reach out to support@simeoncoud.com.

Fixes and Improvements: The Simeon team is always hard at work for you!

  • [Improvement] The AutoExpandingArchiveEnabled property will now export under OrganizationConfig settings
  • [Fix] Prevented an issue where a Sync could error after making changes to the config.tenant.json file in the repository
  • [Fix] Resolved an issue where a Sync could fail on export for graph.macOSPkgApp
  • [Fix] Addressed an issue where Role Assignments could appear to be exported on each Sync
  • [Fix] Configurations that end with a parenthesis number pattern (0) could cause errors when being deployed
  • [Fix] Ensure that Microsoft-managed Conditional Access policies can be updated
  • [Fix] Prevented an issue where OrganizationalBrandingLocalization could fail to deploy due to an invalid property ID
  • [Fix] Prevented issues Syncing groups with the isManagementRestricted property
  • [Fix] Addressed an issue when Syncing an Application with an ID that is the same as the appID
  • [Fix] Addressed an issue where Conditional Access policies could not be validated due to an invalid MAM Policy
  • [Fix] Ensure that all mailboxes are exported correctly when applying a Sync filter
  • [Fix] Improved handling of Managed App Configuration policies to ensure all dependencies are properly included in the Sync

‍

Thanks for Reading

‍

Let us know how we can improve these updates and our platform by emailing us.

‍

Thank You,

‍

Team Simeon


‍