User Profile
VasilMichev
MVP
Joined Jun 23, 2016
User Widgets
Recent Discussions
Re: Finding Forwards based upon to address
There are various forms of forwarding and if you want the solution to be thorough, you have to account for all of them. I have a sample script here: https://michev.info/blog/post/4466/report-on-microsoft-365-mailbox-forwarding-all-methods-via-powershell An easier approach might be to take a look at the Auto-forwarded messages report in the Exchange Online admin center: Auto forwarded messages report in the new Exchange admin center (EAC) in Exchange Online | Microsoft Learn Lastly, you can run a message trace against one of the addresses in order to see how the message was delivered to them: https://learn.microsoft.com/en-us/exchange/monitoring/trace-an-email-message/message-trace-modern-eac21Views0likes0CommentsRe: App-only authentication for unattended scripts in MicrosoftPlaces
The underlying Places API has limited support for application permissions, mostly the READ methods are what's supported. If you meant this as a feature request, the best place to put it is over at the Feedback portal: https://feedbackportal.microsoft.com/feedback/forum/ebe2edae-97d1-ec11-a7b5-0022481f3c8039Views0likes0CommentsRe: How long are kept onlineMeetings data (main teams data, attendanceReports)
As mentioned in the documentation: The expiry time for online meetings is set to 60 days after the meeting's start or end time. If the meeting is updated or activated before it expires, the expiry time will be extended by another 60 days.12Views0likes0CommentsRe: Mail retention - storage of potential duplicate Data
There is no 90% threshold, not sure where you got that from. Messages that are deleted from the main mailbox end up in the Recoverable items subtree and are kept there for the duration of any holds affecting them. When the mailbox has an Online archive, a retention tag is automatically applied to the Recoverable items, moving items older than 14 days to the Recoverable items subtree within the archive. So in effect, you still get space in the main mailbox freed up, after a while. Said tag also ensures that the Recoverable item subtree, which has its own quota independent of the "user" quota, does not get filled up with deleted items. Effectively, with the Online archive you get an extra 100GB quota for the main mailbox and 100GB for the Recoverable items (well 30GB by default, but it changes to 100GB when holds are in play). While less common, you can end up with scenarios where the Recoverable items reaches its quota, thus preventing any item deletions. So having that extra quota helps. This article gives you more detail on how the Recoverable Items construct works: https://learn.microsoft.com/en-us/exchange/security-and-compliance/recoverable-items-folder/recoverable-items-folder After a hold expires, items held within the Recoverable items subtree "age out" and are permanently deleted (cannot be recovered anymore). Items that remain in the "main" mailbox will only be affected if you configured a "retain for XXX days and delete" type of tag - no automatic deletion happens unless an admin takes action to enable it.25Views0likes0CommentsRe: Mail retention - storage of potential duplicate Data
They aren't, who says they are? Archiving does work just fine for retention scenarios, it will free up space in the primary mailbox, including within the recoverable items subtree. Same goes for deleting items, as they will eventually end up in recoverable items and then moved to the associated structure in the archive mailbox.114Views0likes2CommentsRe: Mail retention - storage of potential duplicate Data
There are no files, everything is stored in place, within the mailbox itself. Moving items within the mailbox itself, including to/from any associated archive, does not affect storage. Moving data between mailboxes, or to Groups/Public folders will result in a copy of any moved item being preserved for the duration of the matching retention policy. In other words, if the mailbox is under (generic/blanket) retention policy, all data within is preserved, regardless of any deletions/moves. This is why "cleanup" operations require you to (temporary) disable the retention policy, see for example https://learn.microsoft.com/en-us/exchange/policy-and-compliance/recoverable-items-folder/clean-up-deleted-items Nowadays, we do have the Priority cleanup feature as well, which can help in such scenarios.88Views0likes0CommentsRe: setting up gmail in classic outlook
Make sure that IMAP is indeed enabled within Gmail settings. Classic Outlook supports OAuth, so it can add any Gmail account, even those protected with 2FA or passkeys. If you are using an Outlook version that does not support OAuth, you will have to configure an app password within your Google account instead and use it within Outlook. Both methods are detailed here: https://support.google.com/a/answer/9003945?hl=en466Views0likes1CommentRe: Exchange online - track deleted mail
Audit logs are your best option here, they will clearly indicate who the actor was. And yes, in most cases it's the user itself, or some add-in they allowed. Especially relevant now with AI integrations that helpfully clean up everything in your Inbox :D72Views0likes0CommentsRe: There needs to be a way to disable the Editor for Outlook.
You can disable (most of) the Editor features, though the settings for that are a bit hidden. Start by composing a new message, then on the Ribbon, scroll all the way right to the last group and select Editor > Editor settings. Toggle text predictions, auto-correct and so on as you see fit.88Views1like2CommentsRe: MFA catch-22 during onboarding due to registration policy
You don't need to use the registration policy, even without it the users will be prompted to register methods the first time they try to access any MFA-protected app. Also, you can scope a CA policy to the registration process itself: https://learn.microsoft.com/en-us/entra/identity/conditional-access/policy-all-users-security-info-registration Alternatively, consider using methods such as TAP for the initial account provisioning.109Views0likes0CommentsRe: Adaptive Scope
Are those mail/mailbox enabled users? When talking about CustomAttributeXX, the documentation refers to the set of Exchange attributes, which in turn means that only objects recognized by Exchange can be used with such. If this is a "pure" user object, without any footprint in ExO, you will not be able to use CustomAttributeXX for this purpose, even if its showing as "populated" under OnPremisesExtensionAttributes. Other than that, make sure the user is properly licensed, as adaptive scopes do enforce licensing requirements26Views0likes0Comments
Recent Blog Articles
No content to show