User Profile
esd087
Brass Contributor
Joined 3 years ago
User Widgets
Recent Discussions
Re: Azure Information Protection Premium P1
Bumping this thread up. Microsoft needs to understand that many companies (in my case, an MSP providing licensing to hundreds of clients) used the AIP P1 license solely for email encryption (Purview Message Encryption Basic). Because Microsoft is starting this "journey", aka forcing us to more expensive SKUs, we haven't found a good alternative. Pushing our clients to $22.00 Business Premium licenses is not the answer; even going to a EMS E3 for $10.60 is significantly higher than the $3.00 AIP license. Does Microsoft not have a cheaper add-on alternative for Message Encryption?8.9KViews6likes0CommentsRe: Lighthouse GDAP setup is sending too many email notifications
Thank you, but this was not helpful. The alert rules in Lighthouse apply to setting up alerts on client tenants, not alerts for the partner/reseller that is managing Lighthouse. Inactive users and risky users have nothing to do with what I'm asking.Lighthouse GDAP setup is sending too many email notifications
We (an MSP) are in the process of setting up GDAP relationships via Microsoft 365 Lighthouse, to better manage our clients' tenants. We are also cleaning up old clients from our Microsoft Partner Center customer list and removing GDAP relationships from previous license providers. Through a lot of these GDAP changes, our employees are receiving a TON of GDAP email notifications (ex: "Your granular admin relationship with [Client Name] has been terminated" or "the customer approved your granular admin relationship request"). As best I can tell, this appears to be related to the templates/roles/permissions settings in the Lighthouse GDAP setup. However, I can't specifically find where to change this. What can I change to reduce the number of people in our MSP organization who receive GDAP notifications?SolvedWhat is the best method to migrate Exchange DLP rules to a Compliance DLP Policy?
We have historically used Exchange Mail flow rules to encrypt email for our clients. For example: - Apply this rule if: 1) message is sent outside the organization AND 2) message contains sensitive information (ex: SSN, Credit Card Number, etc.) - Do the following: Rights protect message with RMS template: Encrypt Earlier this year, Microsoft disabled the ability to create/edit DLP policies/rules in Exchange Admin Center. In November, those rules completely stopped working (yes, they likely notified us a long time ago, and yes we're way behind on this ). The recommended action is to "migrate" them to Purview DLP in the compliance center. EDIT: found out the migration wizard is only supported for for ETRs that are *linked* to DLP policies. Reference: comments section here. Our ETRs are not linked to policies. There is documentation (https://learn.microsoft.com/en-us/purview/dlp-migrate-exo-policy-to-unified-dlp) stating that a migration wizard can be used to move the policies. In the tenant where I'm testing, I have the correct licensing (E3) as required in the documentation; I also have Office 365 DLP licenses. However, the migration wizard is not appearing in the Compliance Center > Data loss prevention > policies. I have beat my head against the wall with Microsoft support and have gotten no answers. QUESTIONS: 1. Is there any other way to access the DLP migration wizard other than hoping the banner pops up? (https://learn.microsoft.com/en-us/purview/dlp-migrate-exo-policy-to-unified-dlp under "Migration" #2) (answered above, not available if your ETRs are not linked to a DLP policy) 2. If not, is there any efficient way to move the specific rule mentioned above for several dozen tenants? Perhaps a PowerShell command to create this specific DLP rule that encrypts emails with sensitive content? 3. If not, is there any documentation from Microsoft on how to configure an email encryption policy like this? If we have to manually create the policy (Purview Compliance > Data loss prevention > create policy), the closest action I see is "restrict access or encrypt the content in Microsoft 365 locations".2KViews0likes0CommentsRe: Error when trying to modify or create Exchange Online connectors
MegaVolt - thanks for commenting on this! After several days of trying to set up connectors, the "Set-OutboundConnector" and "Set-InboundConnector" commands worked. I still can't create new connectors, but this worked for existing connectors at least.7.3KViews0likes1Comment
Recent Blog Articles
No content to show