Ken Sicinski’s TechNet Blog https://docs.microsoft.com/archive/blogs/kesicins/feed.xml All Things Exchange and Office 365 Wed, 17 Apr 2019 03:37:24 GMT en-US hourly 1 Use Hashtables to Audit Proxy Addresses Prior to Exchange Online Migration https://docs.microsoft.com/archive/blogs/kesicins/use-hashtables-to-audit-proxyaddresses-prior-to-exchange-online-migration Mon, 11 Jun 2018 16:00:15 GMT https://blogs.technet.microsoft.com/kesicins/?p=65 You can't use the domain because it's not an accepted domain for your organization. I wasn't aware of any built-in reporting in Exchange that would do this, so once I had the requirements of what they were looking for, I went to work in PowerShell. What I found was if we were able to gather the emailAddresses field from all of the mailboxes in the on-premises organization, we could get can accurate count of the various recipient domains are in use within the on-premises Exchange environment. My approach:
  1. Pull all of the mailboxes within Exchange On-premises (this may take a while depending on how many mailboxes you have in your organization), and place in a variable.
  2. Create an empty hashtable.
  3. Declare an "addresses" variable, which will contain all addresses within the EmailAddresses variable on the mailbox.
  4. Create a foreach loop that goes through each value specified within the "addresses" variable.
  5. Create a "pos" (position) variable that will hold the position of the "@" symbol within the SMTP address passed through the loop.
  6. Create a "suffix" variable that will return a substring of the email address (everything after the "@" symbol in the SMTP address).
  7. Add the suffix to the hashtable (if it exists).
  8. Sort the hashtable in descending order, and export to a .txt file.
If all works as expected, a txt file should be created that looks something like this:         From there, we could look at the mailboxes that have these addresses stamped on them and remove as necessary: 
Get-Mailbox -ResultSize Unlimited | ? {$_.EmailAddresses -like *@domain.com*}
Below you will find the proof-of-concept for what is described above for this process. Please note that this script should be tested prior to running in any sort of production environment. SMTPDomains.txt Feel free to leave a comment with any questions you may have. Happy migrating!]]> "You can't access this application" when trying to connect with Exchange Online mailbox through ActiveSync https://docs.microsoft.com/archive/blogs/kesicins/you-cant-access-this-application-when-trying-to-connect-with-exchange-online-mailbox-through-activesync Tue, 02 Jan 2018 11:45:28 GMT https://blogs.technet.microsoft.com/kesicins/?p=36   Selecting "Return to the application without granting consent" (highlighted in the screenshot above) will allow the user to connect to the mailbox via Basic authentication instead of Modern Authentication, but this clearly wasn't working the way we wanted it to.   Now, we've determined that it was an authentication issue within Azure AD, but were initially unable to determine the exact point of failure, as the application "iOS Accounts" was configured to allow authentication against the application for all users (we'd see a "Bad Request" error if the application wasn't authorized permission to connect to the service).   After some digging, we were able to determine the cause of the issue. In the User settings within Azure Active Directory for the tenant, "Users can consent to apps accessing company data on their behalf" was set to "No":     Once we changed this setting, users who were previously experiencing issues with connecting via Modern Auth were able to do so. You can also make this change via Azure AD PowerShell via the Set-MsolCompanySettings cmdlet, and can check the status of the parameter via Get-MsolCompanyInformation: 
Set-MsolCompanySettings -UsersPermissionToUserConsentToAppEnabled $true
]]>