Why I could be marked as spam or phishing email?


Most probably because your message did not pass the DMARC Authentication
Continue reading


Display Exchange Online mailbox information with Office 365 PowerShell

Exchange online powershell
Microsoft online Exchange powershell
Microsoft online Exchange powershell

Display microsoft Exchange Online mailbox information with Office 365 PowerShell

Display Exchange Online mailbox information with Office 365 PowerShell

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic –AllowRedirection
Import-PSSession $Session
Remove-PSSession $Session

Display Microsoft Exchange Online mailbox information with Office 365 PowerShell
Continue reading

Moving mailboxes online Troubleshooting


1    Outlook    1

1.1    Outlook Rules    1

1.    Client-only rules    1

2    Server-side rules    1

3    Mobile Seamless move    2

4    User and password Prompt screen    2



Moving mailboxes online Troubleshooting





First Problem outlook Rules aren’t applied after the moving of exchange mailbox online

This is because some rules are on server and some rules are on the client side when moving the mailbox online some rules have to be recreated and pointing to the destination folders again


  1. Outlook

    1. Outlook Rules

      Office 365 – Server-side vs Client-only Rules

      Client-only rules

          have at least one condition or action that uses an Outlook feature and they don’t run until you log into Outlook with the account that you used to create the rule. For example, this is a client-only rule:

      From <people or distribution list>, flag message to <play a sound>

      In this example, you ask the rule to play a sound when you receive a message and this condition can be performed only by Outlook, which makes it a client-only rule.


    Server-side rules

        use conditions and actions handled by the Exchange server and these rules run whether or not you log into Outlook on your computer. Here’s an example of a server-side rule:

    From <people or distribution list in the GAL or your contacts list>, move it to the <specified> folder

    This rule uses all Exchange server information, like moving a message from a sender who’s in the Global Address List (GAL) to a specific folder that’s in your Exchange mailbox

    user must be in the GAL and we must point to the folder again 



  1. Mobile Seamless move

    Mobile must be configured with default configuration not advanced


  1. User and password Prompt screen

    1. After moving online outlook will as for the credentials for the first time 0nly
    2. Single Sign on – Prompt for Credentials (Default must sign in first time )

Understanding Custom Attributes

Understanding Custom Attributes

Dynamic groups

Microsoft Exchange Server 2010 and Exchange Server 2007 include 15 extension attributes. You can use these attributes to add information about a recipient, such as an employee ID, organizational unit (OU), or some other custom value for which there isn’t an existing attribute. These custom attributes are labeled in Active Directory as ms-Exch-Extension-Attribute1through ms-Exch-Extension-Attribute15. In the Exchange Management Shell, the corresponding parameters are CustomAttribute1 through CustomAttribute15. These attributes aren’t used by any Exchange components. They can be used to store Active Directory data without having to extend the Active Directory schema.

Get-Mailbox -OrganizationalUnit Sales | Set-Mailbox CustomAttribute1 “SalesOU”

Now you can create an e-mail address policy for all recipients that have the CustomAttribute1 property that equals SalesOU, as shown in this example.


New-EmailAddressPolicy -Name “Sales” -RecipientFilter { CustomAttribute1 -eq “SalesOU”} -EnabledEmailAddressTemplates “SMTP:%s%2g@sales.contoso.c

For Dynamic Groups

When creating dynamic distribution groups, e-mail address policies, or address lists, you don’t need to use the RecipeintFilter parameter to specify custom attributes. You can use theConditionalCustomAttribute1 to ConditionalCustomAttribute15 parameters instead. You can create a dynamic distribution group based on the recipients whose CustomAttribute1 is set to SalesOU, as shown in this example.

New-DynamicDistributionGroup -Name "Sales Users and Contacts" -IncludedRecipients "MailboxUsers,MailContacts" -ConditionalCustomAttribute1 "SalesOU"


Ref: https://technet.microsoft.com/en-us/library/ee423541(v=exchg.141).aspx

How to add custom attributes to rules in Dynamic Exchange Groups Exchange

Open exchange management shell run the following


Get-DynamicDistributionGroup “DynamicGroupName” | Fl


Then run the following

set-DynamicDistributionGroup “DynamicGroupName” -CustomAttribute1 DDL

Get-DynamicDistributionGroup “groupName” | FL

To make sure it worked

In this scenario only dynamic groups will be added as members of another dynamic group


To set all custom attribute of dynamic groups to same value

Get-DynamicDistributionGroup | set-DynamicDistributionGroup -CustomAttribute1 DDL

$DDG = Get-DynamicDistributionGroup “Groupname”

Get-Recipient -RecipientPreviewFilter $DDG.RecipientFilter

Grand permission for on prem public folder or shared mailbox to office 365 users

First create universal group and add users to the group the mail enable it

With the following command from the exchange PowerShell

Enable-DistributionGroup -Identity “groupName”

After its enabled

Run the following command

send on behalf off

(run the command from the exchange powershell)

Set-MailPublicFolder “\publicfoldername” -GrantSendOnBehalfTo “Groupname”

send as

For the send as go to properties of the distribution  group from the ECP schange link then go to delivery options

Add the group