How to Create Public Folder’s in Office 365 W15


The Public Folders pages is a new feature for Exchange Online introduced with Office 365 Preview. It provides an easy and effective way to collect, organize, and share information with other people in your workgroup or organization. It is not designed for Archiving Data or Document sharing and Collaboration.

In Office 365 Preview every public folder must live in a Public Folder mailbox. You will need to create at least one Public Folder mailbox before you can create Public Folders.

To create a Public Folder Mailbox
Navigate to the Exchange Admin Center (EAC)

Click Public Folders > Public Folder Mailboxes > Click (+) New

Enter a Name and click Save

Check the list to ensure the new Public Folder Mailbox is available

To create a Public Folder
Click Public Folders > Public Folders > Click (+) New

Enter a Name and click Save.

Verify that the folder has been created

In the Public Folder window, note that several new options will be available, e.g:

  • General: Public Folder name etc
  • Statistics: Count of Deleted Items etc
  • Limits: Warning Quotas etc
  • General mail properties: Edit Alias, Display Name, add custom attributes
  • Emails Addresses: Add/Edit additional SMTP Addresses for the public folder
  • Member Of: Add the public folder to distribution groups
  • Delivery Options: Configure Send As, Send on behalf, and Forwarding on the public folder
  • Mail Flow Settings: Enable/Edit delivery restrictions on for the public folder mailbox.

To view Public Folders on Outlook 2013, navigate near to Tasks and you’ll see "………" > click on "…….." and choose Folders

Now you can view your Public Folders on Outlook 20013

Note

  • Kiosk plan users are not licensed for public folders
  • You are limited to 50 public folder mailboxes with a maximum size of 1.25 TB.
  • See the Exchange Online Service Description for more

How To: Give Users Send As Permission


Send As permission, also known as SendAs permission, gives a user permission to use another recipient’s e-mail address in the From address. For example, when you give the user Chris Send As permission on the mailbox of a user named Michelle, Chris can send e-mail messages that appear to be sent by Michelle, with no indication to the recipient that anyone other than Michelle sent the message. Or, if your organization uses a Help Desk distribution group, you can give Help Desk staff Send As permission on the Help Desk distribution group. That way, replies to messages sent to the Help Desk group appear to come from the group instead of an individual Help Desk technician.

To give a user Send As permission, you use Windows PowerShell

Before you begin

  • To learn how to install and configure Windows PowerShell and connect to the service, see Use Windows PowerShell in Exchange Online.
  • The Send As permission is different than the Send on Behalf permission. If the user Chris has Send on Behalf permission on Michelle’s mailbox, when Chris sends an e-mail as Michelle, the From address shows Chris on behalf of Michelle. Microsoft Outlook users can configure Send on Behalf permissions on their own mailbox using delegates. Administrators can configure Send on Behalf permissions on any recipient type using the GrantSendOnBehalfTo parameter.
  • Want more information about parameters? See An explanation of parameters.

Give a user Send As permission
Launch Windows PowerShell and perform the following steps:

Import-Module msonline 
$cred = Get-Credential 
Connect-MsolService -cred $cred 
Get-Command –Module msonline

1) Import the module.
2) Create a credential-object stored in the variable $credimp
3) Create a new remote PowerShell connection against the PowerShell endpoint for Office 365
4) List the cmdlets available

A shortcut to the module is also available on the Start-menu (you can skip step 1 if launching this shortcut):

Run the following command:
Command:
Add-RecipientPermission <identity> -AccessRights SendAs -Trustee <user>

For example, to give the user named Joanna Vathis Send As permission for the Test mailbox , run the following command:
Example:
Add-RecipientPermission test@itprodev.onmicrosoft.com  -AccessRights SendAs -Trustee joannav@itprodev.onmicrosoft.com

       OR
Command:
Add-RecipientPermission "TEST" -AccessRights SendAs -Trustee "Joanna Vathis"
Joanna can now send messages that appear to come directly from the TEST mailbox.
Note  By default, you are asked to confirm the addition of the Send As permission. To skip the confirmation prompt, use -Confirm:$false.

View Send As permissions

Use the Get-RecipientPermission cmdlet to display all the Send As permissions configured in your organization. You can filter the list to show Send As permissions granted to a specific user and to see the Send As permission on a specific recipient.

View Send As permission for a specific user

Run the following command:
Command:
Get-RecipientPermission – Trustee <user>
For example, to list the recipients for whom the user named Kim Akers has Send As permission, run the following command:
Command:
Get-RecipientPermission -Trustee joannav@itprodev.onmicrosoft.com
Joanna can send messages that appear to come directly from the recipients

View Send As permission on a specific recipient

Run the following command:
Command:
Get-RecipientPermission <identity>

For example, to list the users who have Send As permission on the TEST mailbox, run the following command:
Command:
Get-RecipientPermission "TEST"
The users listed can send messages that appear to come directly from the TEST mailbox.


View all Send As permissions you’ve configured in your organization

Run the following command:
Command:
Get-RecipientPermission | where {($_.Trustee -ne ‘nt authority\self’) -and ($_.Trustee -ne ‘null sid’)}

Note The filter hides the automatic Send As permission that allows a user to send messages from their own mailbox, and also any results from system objects like mailbox plans.


Revoke Send As permission

Run the following command:
Command:
Remove-RecipientPermission <identity> -AccessRights SendAs -Trustee <user>

For example, to revoke Joanna’s Vathis Send As permission for the TEST mailbox, run the following command:
Command:
Remove-RecipientPermission "TEST" -AccessRights SendAs -Trustee joannav@itprodev.onmicrosoft.com

Now Joanna can’t send messages that appear to come directly from the TEST mailbox.
To skip the confirmation prompt, use -Confirm:$false.

How people use the Send As permission

Individual users or members of security groups with Send As permission can open their own mailboxes and send messages using the From address of the recipient.
Send As permission doesn’t give a user access to another user’s mailbox. To give an individual or members of a security group access to a mailbox, use the following command:
Command:
Add-MailboxPermission <mailbox> -User <user or security group> -AccessRights FullAccess

When you give someone access to a mailbox and Send As permission on the mailbox, that person can open the mailbox using their own credentials, compose new messages, and reply to messages in the mailbox.
An explanation of parameters
You use the Add-RecipientPermission, Remove-RecipientPermission, and Get-RecipientPermission cmdlets to add, remove and view Send As permissions. These cmdlets use the same basic parameters:

Identity This parameter specifies the target recipient. The user or group specified by the Trustee parameter can operate on this recipient.
You can specify any type of recipient. For example:

  • Mailboxes
  • Mail users
  • External contacts
  • Distribution groups
  • Dynamic distribution groups
    The Identity parameter is a positional parameter. The first argument on a cmdlet is assumed to be the Identity parameter when no parameter label is specified. This lets you specify the parameter’s value without specifying the parameter’s name.

Trustee This parameter specifies the user or group to whom you’re granting the permission. This allows the user or group to operate on the recipient specified by the Identity parameter.
You can specify the following types of users or groups:

  • Mailbox users
  • Mail users with a user account
  • Security groups

For the Identity and Trustee parameters, you can use any value that uniquely identifies the recipient.

For example:

  • Alias
  • Distinguished name (DN)
  • GUID
  • Name
  • Display name
  • LegacyExchangeDN
  • E-mail address

Additional Information’s:

Give Users Send As Permission
http://help.outlook.com/en-us/140/ff852815.aspx

How to get the list for SMTP address and Last connection time for all the users


Summary
This article describes how to use PowerShell Commandlet to get the list for SMTP address and Last connection time for all the users.

Steps to implement the request
Step 1: Run the following to authenticate yourself and import PowerShell commands to your local session:

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

  
Image 1

Step 2: Run the Commandlet to get the SMTP address and Last connection time for all the users
Commandlet to get SMTP address:
Get-Mailbox | fl EmailAddresses, identity > C:\Emailaddress.csv


Image 2


Image 3


Image 4

Commandlet to get Last connection time:
Get-Mailbox -ResultSize unlimited | Get-MailboxStatistics | select-object identity,lastlogontime,lastlogofftime,DisplayName | sort-object DisplayName -descending | export-csv C:\Lastlogontime.csv

  
Image 5


Image 6


Image 7

Enjoy Wink

Mail Protection Reports for Office 365


This reporting workbook provides you with a detailed view into the email protection data that is available in the Office 365 Reporting dashboard.
This workbook is available to all Exchange Online and Exchange Online Protection customers. The workbook provides summary graphs for a number of different types of email message filtering.
This includes messages identified as spam, malware, or good mail (mail that cleanly passed all filtering). It also shows graphs for messages that were identified by either a transport rule or DLP policy (Exchange Online customers only).
The data for the summary graphs is pulled locally via a web service call. After loading the summary data into the workbook, you can perform deeper analysis through the use of data slicers.
These allow you to change the view of the data in order to identify trends or unusual activity. When such a condition is found, you can click through from the summary to the detail data.
Another web service call will be made to pull the detail data that you can use to identify the actual messages that caused the condition seen in the summary graph.


Bellow you can see the installation instruction’s

After completing the installation, open the workbook in Excel 2013 using the shortcut on your desktop and login with your Administrator Office 365 credential’s and click on Query

After the scanning finished, check the results

EnjoyWink

Microsoft Exchange 2013 Public Folders Migration Scripts


    Microsoft recently release the necessary support scripts to migrate Exchange 2007/2010 Public Folders to Office 365.

Microsoft Exchange 2013 Public Folders Migration Scripts

  • Use these scripts to migrate public folders from Exchange 2010 or 2007 to Exchange 2013.
  • In order to migrate Exchange 2010 or 2007 Public Folders to Exchange 2013 on O365, we need to analyze the existing
    Public Folder hierarchy for size to figure out the number of Public Folder mailboxes that are required on O365 and the distribution of folders across mailboxes.

Microsoft Exchange 2013 Public Folders Directory Sync Support Scripts

  • Use this scripts if you need to do one of the following 
  • Initial creation of mail enabled public folder objects in the destination Active Directory for public folder migration from Exchange 2007 or 2010 to Exchange 2013
  • Synchronization of mail enabled public folder objects from cloud to on premise Active Directory
  • Synchronization of mail enabled public folder objects from on premise to cloud Active Directory
  • Synchronization of public folder mailbox objects from cloud to on premise Active Directory