Give people delegate permissions for a distribution group Office 365

 

 

Give people delegate permissions for a distribution group

If you are an Office 365 admin, you can give people delegate permissions to send email from, and on behalf of a distribution group.

1. Log in to your office 365 admin center.
2. Click the Admin tile.
3. In the Office 365 admin center panel, click Groups.
4. In the Groups panel, check the box next to the group you want to add delegates to.
5. In the right panel, under Distribution list, click Edit Exchange properties.
6. Click group delegation.
7. Use the following to help you determine whether you want to assign Send As or Send on Behalf permissions

Send As:

This allows a member of the group to send email as the distribution group address. To a recipient, the From line will display the group name only.

Send on Behalf:

This allows a member of the group to send email on behalf of the group. To a recipient, the From line will display the sender “on behalf of” the group.

To send as the distribution group, you need to show the From field in your email composer. To show the From field in Outlook, open a new email, click Options, and select From.

Source: Give people delegate permissions for a distribution group | Office 365 from GoDaddy – GoDaddy Help GB

Prevent false positive email marked as spam in office 365

Tips for Office 365 Admins to prevent good email marked as spam from being sent to quarantine as a false positive. Customize a safelist and other options to prevent good email marked as spam.

1. Obtain the headers for the message you want to allow in your mail client such as Outlook or Outlook Web App, as described in Message Header Analyzer.

1. Open the message.
2. Go to Options > properties.
3. Copy the internet headers section.
4. Go to Message Header Analyzer.
5. Paste the internet headers section.
6. Click analyze

1. Search for the IP address following the CIP tag in the X-Forefront-Antispam-Report header manually or by using the message header analyzer.
2. Add the IP address to the IP Allow list by following the steps in “Use the EAC to edit the default connection filter policy” in Configure the connection filter policy.
3. In the Exchange admin center (EAC), navigate to Protection > Connection filter, and then double-click the default policy.
4. Click the Connection filtering menu item and then create the lists you want: an IP Allow list, an IP Block list, or both.
5. Click  . In the subsequent dialog box, specify the IP address or address range, and then click ok. Repeat this process to add additional addresses. (you can also edit or remove IP addresses after they have been added.)
6. Optionally, select the enable safe list check box to prevent missing email from certain well-known senders. How? Microsoft subscribes to third-party sources of trusted senders. Using this safe list means that these trusted senders aren’t mistakenly marked as spam. We recommend selecting this option because it should reduce the number of false positives (good mail that’s classified as spam) you receive.
7. Click save. A summary of your default policy settings appears in the right pane.

• Note:
• If you add an IP address to both lists, email sent from it is allowed.
• IPv4 IP addresses must be specified in the format nnn.nnn.nnn.nnn.
• You can also specify classless inter-domain routing (cidr) ranges in the format nnn.nnn.nnn.nnn/rr.
• You can specify a maximum of 1273 entries, where an entry is either a single IP address or a cidr range of IP addresses from /24 to /32.

 

Source: Prevent false positive email marked as spam with a safelist or other techniques – Office 365

 

Manage Office 365 Forward Mail in PowerShell

Manage Forward Mail by using PowerShell | Office 365

<#

this script set Automatic mail Forwarding to Recipient in office 365

#>

#start script

##########################

#$user=’internal user idestity’ #the source internal user to forward emails from
#$destemail=’internal user email destination address’ #internal destination user to forward emails to
#$destemailext=’xxx@gmail.com’ #external destination email address to forward emails to
#$DisplayName’MailContact Display Name’ #MailContact Display Name
#$mailintext=’Office 365 User Email ‘ #<Office 365 User Email Address for external user (MailContact)

##########################

#Connect to Exchange Online Office 365 using remote 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

##########################

#Forward Email to internal Recipient & DONT saves local copy
#Set-Mailbox $user -ForwardingAddress $destemail -DeliverToMailboxAndForward $False

##########################

#Forward Email to internal Recipient & save local copy (Default)
#Set-Mailbox $user -ForwardingAddress $destemail

##########################

#Forward Email to External Recipient & save local copy (Default)
#Set-Mailbox $user -ForwardingsmtpAddress $destemailext

##########################

#Forward Email to External Recipient & DONT saves local copy
#Set-Mailbox $user -ForwardingsmtpAddress $destemailext -DeliverToMailboxAndForward $False

##########################

#Create External contact with internal email address + Forward email address (External Email Address)
#Step 1: Create External contact with External email address
#New-MailContact -Name $DisplayName -ExternalEmailAddress $destemailext
#Step 2: Set External contact email address to internal email address and forwarding email address (External email address) PowerShell command syntax:
#New-MailContact $DisplayName -emailaddresses SMTP:$mailintext, $destemailext

##########################

#Display information about Forwarding rule
#Get-Mailbox $user

##########################

#Display more information about Forwarding rule
#Get-Mailbox John | FL DeliverToMailboxAndForward,ForwardingAddress,ForwardingSmtpAddress

##########################

#Find all users with Forwarding Address is set to Internal Recipient
#Get-Mailbox | Where {$_.ForwardingAddress -ne $Null} | Select Name, ForwardingAddress, DeliverToMailboxAndForward

##########################

#Turn off Email Automatic Forwarding to internal Recipient
#Set-Mailbox $user -ForwardingAddress $Null

##########################

#Turn off email Automatic Forwarding to External Recipient
#Set-Mailbox $user -ForwardingSmtpAddress $Null

##########################

#Forward Email of ALL Users to internal Recipient & save local copy
#Step 1: Save local copy
#Get-Mailbox | Where {$_.RecipientType -eq “UserMailbox”}| Set-Mailbox -DeliverToMailboxAndForward $True
#Step 2: Forward email to the destination recipient (internal\organization recipient)
#Get-Mailbox | Where {$_.RecipientType -eq “UserMailbox”}| Set-Mailbox -ForwardingAddress $destemail

##########################

#Forward Email of ALL Users to External Recipient & save local copy
#Step 1: Save local copy
#Get-Mailbox | Where {$_.RecipientType -eq “UserMailbox”}| Set-Mailbox -DeliverToMailboxAndForward $True
#Step 2: Forward email to the destination recipient (external recipient)
#Get-Mailbox | Where {$_.RecipientType -eq “UserMailbox”}| Set-Mailbox -ForwardingSmtpAddress $destemailext

##########################

#Turn off email Automatic Forwarding to External Recipient
#Get-Mailbox | Where {$_.RecipientType -eq “UserMailbox”}| Set-Mailbox -ForwardingAddress $Null

##########################

#verify that the email is set to forword
#Get-Mailbox $user| FL DeliverToMailboxAndForward,ForwardingAddress,ForwardingSmtpAddress

##########################

#end Exchange Online Office 365 remote PowerShell Session
#Remove-PSSession $Session

#end script

Office365: Set maximum attachment/email size

Hopefully this helps someone else out there; the amount of PowerShell commands and cmdlets can be quite overwhelming, and knowing what add-on you need for PowerShell to manage your Office365 installations can be a big time waster. Here’s my notes.

1. Windows 7 comes with Powershell v2 as part of the package, and Win8 comes with v3. If you’re using Vista or XP you’ll have to update to at least v2 but that’s outside of this post.

2. Install Microsoft Online Services Sign-On Assistant for IT Pros:

http://www.microsoft.com/en-us/download/details.aspx?id=39267&fwLinkID=286152

(32-bit for 32-bit OS, 64-bit for 64-bit OS)

3. Install Windows Azure AD Module (may be unnecessary for this procedure, but will be necessary for others – I install it by default)

http://technet.microsoft.com/en-us/library/jj151815.aspx

4. Reboot after install.

5. Start Powershell as admin (you will notice a new program group-Windows Azure Active Directory with a Powershell shortcut; it’s safe to start this or the main Powershell program for our purpose).

6. Once in PS, and having your admin credentials for your Office365 subscription, enter the following commands;

$LiveCred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $LiveCred -Authentication Basic –AllowRedirection

Import-PSSession $Session

Get-TransportConfig

‘ now – pay special note to the output from this last command, “Get-TransportConfig” – look for the lines “InternalDsnMaxMessageAttachSize” and “ExternalDsnMaxMessageAttachSize”. This is your current max for outbound and inbound emails. Most likely it’s at 10MB, and not what you want.

Set-TransportConfig -InternalDsnMaxMessageAttachSize (nn)MB

‘ change the (nn) to a number – in meagabytes – that you want for your maximum. Might be 20, 40, etc… supposedly the global max is 25.

Set-TransportConfig -ExternalDsnMaxMessageAttachSize (nn)MB

‘ again, see above note on what to replace (nn) with…

Get-TransportConfig

‘ now check your config – you should see your new max sizes replaced with what you programmed.

Office365: Set maximum attachment/email size.

How to Purchase Licenses in Office 365

1.    In the Admin center, click purchase services on the left hand side. On this page, you will be able to purchase your Dynamics CRM Online and Office 365 licenses.

2.    Customize your order by choosing the number of licenses you’d like to order. You have optional add-ons to select from before checking out. Once you have the number of licenses you want, click check out.

3.    Follow the three steps Microsoft lays out for you to purchase your licenses. If you would like to add more licenses or purchase more licenses or add other Office 365 plans to your subscription, you can do so in the purchase services section in the admin center.

·         To drop a license or subscription from your account, you will need to open a service request ticket with Microsoft. You’ll want to open the ticket under the billing department.

Purchasing Licenses in Office 365 | The CRM Book.

Use PowerShell to Explore Office 365

Use PowerShell to Explore Office 365

1. Type Connect-MsolService
2. Enter your office 365 credentials.
3. Type Get-Command -Module MSOnline to see all available commands.

Examples:

To see your package and licenses:

PS C:\Users\guy.naftaly> Get-MsolAccountSku |ft -AutoSize

 

AccountSkuId         ActiveUnits WarningUnits ConsumedUnits

————         ———– ———— ————-

xxxxxxx:MIDSIZEPACK 61          0            44

How to Staged migration mailbox To Office 365

Staged migration

Staged migration enables migration from an on-premises Exchange 2003 or

Exchange 2007.

1.     Prepare a CSV file.

 

Attributes

---

Here are the attributes for each mailbox. The CSV file can only contain these attributes.

EmailAddress specifies the primary SMTP e-mail address for users’ on-premises mailbox. For example, pilarp@tailspintoys.com. This attribute is required.

Important   Be sure to use the primary SMTP address for on-premises mailboxes and not user IDs from the cloud-based organization. For example, if the on-premises domain is named tailspintoys.com but the cloud-based e-mail organization is named service.tailspintoys.com you would use the tailspintoys.com domain name for e-mail addresses in the CSV file.

Password is the password that will be set on the new cloud-based mailbox. Any password restrictions that are applied to your cloud-based organization apply to the passwords included in the CSV file. For more information, see Password Guidelines. This attribute is optional.

ForceChangePassword specifies whether a user must change the password the first time they sign in to their new cloud-based mailbox. Use either True or False for the value of this parameter. Other values are invalid. This attribute is optional.

Important   If you’ve implemented a single sign-on solution by deploying Active Directory Federation Services 2.0 in your on-premises organization, you must use False for the value of the ForceChangePassword attribute.

CSV file format

---

Here’s an example of the format for the CSV file. In this example, three on-premise mailboxes are migrated to the cloud.

EmailAddress,Password,ForceChangePassword

pilarp@tailspintoys.com,Pa$$w0rd,False

tobyn@tailspintoys.com,Pa$$w0rd,False

iant@tailspintoys.com,Pa$$w0rd,False

The first row, or header row, of the CSV file lists the names of the attributes, or fields, specified in the rows that follow. Each attribute name is separated by a comma.

Each row under the header row represents one user and supplies the information that will be used to migrate the user’s mailbox. The attribute values in each row must be in the same order as the attribute names in the header row. Each attribute value is separated by a comma.

Use any text editor, or an application like Microsoft Office Excel, to create the CSV file. Save the file as a .csv or .txt file.

2. Sign in to the Office 365 portal (https://portal.office.com).
3. Click Admin, and then click Exchange.
4. Click Migration, click New (

), and then click Onboarding.

5. Select the migration option that you want, and then click Next. Migration options are as follows:
   1. Remote move
   2. Staged migration
   3. Cutover migration
   4. IMAP

6.     On the “Select the mailboxes” screen, locate the CSV file that you created in step 1, and then click Next.

7.     Enter the credentials of your on-premises admin account, and then click Next.

8.     Enter a name for the migration batch, and then click Next. 

9.      Specify the admins in your Office 365 organization who should receive the migration report, select one of the following migration methods, and then click New:

 

1. Automatically start the migration
2. Manually start the migration later

via How to migrate mailbox data by using the Exchange Admin Center in Office 365.

http://help.outlook.com/en-us/140/ff959691(d=lightweight).aspx

How To Restore User Mailboxes in Office 365

Restore one or more users

When you restore a user account within 30 days after deleting it, the user account and all associated data are restored. The user can sign in to Office 365 with the same user ID, their mailbox is fully restored, and they have access to all services they previously accessed.

Before you restore a user account, make sure there are Office 365 licenses available that you can assign to the account. Also, when you restore an account, you may encounter conflicts with user names or proxy addresses, which you can resolve.

To restore one or more users

1. Go to Admin > Office 365 > Users and groups > Deleted users.
2. On the Deleted users page, choose the names of the users that you want to restore, and then click Restore users.
3. In the confirmation box, click Close.

Delete or restore users – office365 suite.

How Connect to Exchange Online Office 365 using remote PowerShell

Remote PowerShell allows you to manage your Exchange Online settings from the command line. You use Windows PowerShell on your local computer to create a remote Shell session to Exchange Online. It’s a simple three-step process where you enter your Exchange Online credentials, provide the required connection settings, and then import the Exchange Online cmdlets into your local Windows PowerShell session so that you can use them.

 

What do you need to know before you begin?

·        

Estimated time to complete: 5 minutes

·         You can use the following versions of Windows:

o    Windows 8 or Windows 8.1

o    Windows Server 2012 or Windows Server 2012 R2

o    Windows 7 Service Pack 1 (SP1)*

o    Windows Server 2008 R2 SP1*

·         You need to install the Microsoft .NET Framework 4.5 or 4.5.1 and then either the Windows Management Framework 3.0 or the Windows Management Framework 4.0.

 

Connect to Exchange Online

 

1.     On your local computer, open Windows PowerShell and run the following command.

2.     $UserCredential = Get-Credential

In the Windows PowerShell Credential Request dialog box, type your Exchange Online user name and password, and then click OK.

3.     Run the following command.

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

5.     Run the following command.

6.     Import-PSSession $Session

7.     Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell

               Remove-PSSession $Session

How do you know this worked?

 

After Step 3, the Exchange Online cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don’t receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet—for example, Get-Mailbox—and see the results.

If you receive errors, check the following requirements:

·         A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.

·         To help prevent denial-of-service (DoS) attacks, you’re limited to three open remote PowerShell connections to your Exchange Online organization.

·         Windows PowerShell needs to be configured to run scripts. You only need to configure this setting once on your computer, not every time you connect. To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you opened by selecting Run as administrator).

·         Set-ExecutionPolicy RemoteSigned

 

·         The account you use to connect to Exchange Online must be enabled for remote Shell. TCP port 80 traffic needs to be open between your local computer and Exchange Online. It’s probably open, but it’s something to consider if your organization has a restrictive Internet access policy.

Connect to Exchange Online using remote PowerShell: Exchange Online Help.

How To Delete User Mailboxes in Office 365

·         You can delete Exchange Online mailboxes by deleting the corresponding Office 365 user account, removing the Exchange Online license, or by running the Remove-Mailbox cmdlet in the Shell.

·         When a mailbox is deleted, Exchange Online retains its contents for 30 days, by default. After 30 days, the mailbox is permanently deleted and is not recoverable.

·         You can recover a deleted mailbox within the retention period by using the Office 365 admin center to recover the corresponding Office 365 user account.

·         If the mailbox was deleted by removing the Exchange Online license, it can be restored within the retention period by reassigning the license to the corresponding user account. 

·         If you need to delete a mailbox, but preserve the mailbox contents indefinitely, you can enable an inactive mailbox. To do this, you have place the mailbox on In-Place Hold before you delete it. 

·         Before an inactive mailbox can be enabled, the mailbox must be assigned an Exchange Online (Plan 2) license or have an Exchange Online Archiving subscription so that an In-Place Hold can be placed on the mailbox before it’s deleted.

Use the Office 365 admin center to delete a user account

1.     Go to Admin > Office 365 > Users and groups.

2.     Choose the names of the users that you want to delete, and then click Delete .

3.     In the confirmation box, click yes.

Use the Shell to delete a mailbox

1.     Connect to Exchange Online Using Remote PowerShell:

a.     Run PowerShell as administrator.

b.    Configure PowerShell to run scripts. Set-ExecutionPolicy RemoteSigned

c.     $UserCredential = Get-Credential

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

e.     Import-PSSession $Session

2.     Remove-Mailbox -Identity “Nellie Rom”

3.     Disconnect the remote PowerShell session:

 

a.     Remove-PSSession $Session

via Delete or Restore User Mailboxes in Exchange Online: Exchange Online Help.