All you want to know about Office 365 in the Other region / Middle east region – Information is wealth ……… Share it! ……… PREMNAIR
Limitations: Office 365 – what user/admin should know…
Once you migrated to O365 platform..you should know the following
Message limit: The maximum total size of an e-mail message is 25MB. This total size includes the message header, the message body, and any file attachments. An e-mail client may limit the size of an individual file attachment to a value much less than the message size limit. The maximum number of file attachments allowed in an e-mail message is 125 attachments. The maximum number of text characters allowed in the subject line of an e-mail message is 255 characters. The maximum number of message body parts that are allowed in a MIME multipart is message is 250 parts. The maximum number of forwarded e-mail messages that are allowed in an e-mail message is 30.
Recipient and sender limits: These limits are applied to messages, senders, or recipients to combat spam and mass-mailing worms or viruses. The maximum number of message recipients allowed in the To:, Cc:, and Bcc: fields is 500 receipents. The maximum number of e-mail messages that can be sent from a single e-mail client per minute is 30 messages. The maximum number of recipients that can receive e-mail messages sent from a single cloud-based mailbox in a 24 hour period is 1,500 receipients per day. After the limit has been reached, messages can’t be sent from the mailbox until the number of recipients that were sent messages in the past 24 hours drops below the limit.
Retention limits: The maximum number of days that items can remain in the Deleted Items folder before they are automatically removed is 30 days. The maximum numbers of days that items removed from the Deleted Items folder are retained before they are permanently deleted is 14 days. The maximum number of days that items can remain in the Junk E-mail folder before they are automatically removed is 30 days
Distribution group limits: Maximum number of distribution group members is 100,000 members. Limit sending messages to large distribution groups is 5,000 or more members. If a message is sent to 5,000 or more recipients, the message size can’t exceed this limit (2MB). If the message size exceeds the limit, the message isn’t delivered, and the sender receives a non-delivery report (NDR). The total recipient count is determined after distribution group expansion.
Transport rule limits: The maximum number of rules that can exist in the organization is 100 rules. The maximum number of characters that can be used in a single transport rule. The characters are used in the conditions, exceptions, and actions is 4,000 characters. The total number of characters used by all the regular expressions in all the transport rule conditions and exceptions in the organization is 20,000 characters. Maximum number of recipients added to a message by all transport rules is 100 receipients.
Moderation limits: Maximum size of the arbitration mailbox is 10GB. The maximum number moderators that you can assign to a single moderated distribution group or that can be added to a message using a single transport rule is 10 moderators. Expiration for messages waiting for moderation is 2 days. Maximum rate for expired moderation notification messages is 300 expiration notifications per hour.
Public Folders: What do I do with public folders? The answer depends on if they are mail-enabled or not. Office 365 doesn’t support public folders, but you can move them to shared mailboxes or — if they are not mail-enabled — to SharePoint Online. Cloud based mailbox won’t have access to public folders located in the on-premises Exchange on a hybrid scenario.
Requirements: Office 365 – what user/admin should know…
Client requirements for O365: Recommed to use Microsoft Office outlook 2010 for the best experience. Outlook 2007 latest pack will support the O365. Pre-outlook 2007 clients are not supported. Also please see the requirements for O365 client side readiness
Requirements for single sign-on..To use single sign-on, you must: (also click here to read more Software requirements for Office 365)
Requirements for AD FS 2.0: Active Directory Federation Services (AD FS) 2.0 deployment can collaborate successfully, you must first make sure that your corporate network infrastructure is configured to support AD FS 2.0 requirements for accounts, name resolution, and certificates.
Minimum requirement: Single-core, 1 gigahertz (GHz), 1GB RAM, 50MB Disk Space.
Recommended requirement: Quad-core, 2 GHz , 4GB RAM, 100 MB Disk Space
Network Service: network services is critical for successful deployment of AD FS 2.0 in your organization. AD FS 2.0 to function, TCP/IP network connectivity must exist between the client; a domain controller; and the computers that host the Federation Service and the Federation Service Proxy.
Attribute Store: AD FS 2.0 requires at least one attribute store to be used for authenticating users and extracting security claims for those users. AD FS 2.0 automatically creates an Active Directory attribute store, by default. AD FS 2.0 to operate successfully, domain controllers in either the account partner organization or the resource partner organization must be running Windows Server 2003 SP1, Windows Server 2003 R2, or Windows Server 2008. When AD FS 2.0 is installed and configured on a domain-joined computer, the Active Directory user account store for that domain is made available as a selectable attribute store. AD FS 2.0 does not require schema changes or functional-level modifications to AD DS. AD FS 2.0 integrates naturally with existing Windows authentication