Liongard Ideas Portal

Submit and upvote ideas to make Liongard better. You get 20 votes so vote wisely. 🙂


The Product Team is constantly reading your ideas and while we can’t promise that all ideas will become a reality, we value your feedback and promise to always have our Partners in mind when building and improving Liongard.

Check out our FAQs to learn more.

See what we've shipped by clicking here!

Capture smtp aliases in M365

Having assigned aliases would be incredibly helpful for situations where a user errantly has a license removed and needs to have aliases rebuilt. Also it would be fantastic for hunting to see who has an alias assigned to them - currently you either have to hunt one by one or else pull up powershell

  • David Coles
  • Nov 19 2020
  • Already exists
Last Reviewed Date 2022-07-25
  • Jul 25, 2022

    Admin response

    Hi Everyone! Thank you for your votes. Currently retrieving SMTP alias's is a possibility in the Microsoft 365 Inspector. This data is located in the data print under each `User` object. User[].proxyAddresses . You can also make this value viewable in the UI by enabling the Proxy Addresses column in the inspector's user data table.

  • Attach files
  • Dan Engbers commented
    5 Jan, 2021 01:08am

    Here, try this query and turn on Change Detection.

    Users[?mail != `null`] && Users[?userType == `Member`].join(', ', [to_string(displayName), to_string(mail),to_string(proxyAddresses[])])| join(' | ' @)

    Also built off this one to check Guest accounts and also monitor for changes.

    Users[?userType == `Guest`].join(', ', [to_string(displayName), to_string(mail)])| join(' | ' @)
  • Dan Engbers commented
    5 Jan, 2021 12:46am

    Could you not create a metric for this? Users>Object>proxyAddresses

    I might work on this, it sounds like a good idea. If I can make it work I'll repost here.

  • Schyler Jones commented
    9 Dec, 2020 06:20pm

    I would add that there are other situations that could lead to aliases being wiped, but just in general, it's a good way to round-out the documentation. We recently setup our first Azure AD sync with our own on-premise AD and when we did that we lost aliases for more than one user, and had to "rebuild" them from the AD side. Unfortunately the aliases were not documented so the rebuild was completely from memory.