Updates from: 07/17/2021 03:10:29
Category Microsoft Docs article Related commit history on GitHub Change details
commerce Allowselfservicepurchase Powershell https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/subscriptions/allowselfservicepurchase-powershell.md
search.appverid:
- MET150 description: "Learn how to use the AllowSelfServicePurchase PowerShell cmdlet to turn self-service purchase on or off." Previously updated : 03/18/2021 Last updated : 07/16/2021 # Use AllowSelfServicePurchase for the MSCommerce PowerShell module
The following table lists the available products and their **ProductId**.
| Project Plan 3 | CFQ7TTC0KXNC | | Visio Plan 1 | CFQ7TTC0KXN9 | | Visio Plan 2 | CFQ7TTC0KXN8 |-
+| Windows 365 Enterprise | CFQ7TTC0HHS9 |
+| Windows 365 Business | CFQ7TTC0J203 |
+| Windows 365 Business with Windows Hybrid Benefit | CFQ7TTC0HX99 |
## View or set the status for AllowSelfServicePurchase After you view the list of products available for self-service purchase, you can view or modify the setting for a specific product.
compliance Customer Key Availability Key Understand https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/customer-key-availability-key-understand.md
Microsoft employs a defense-in-depth strategy to prevent malicious actors from i
Microsoft 365 is built to prevent misuse of the availability key. The application layer is the only method through which keys, including the availability key, can be used to encrypt and decrypt data. Only Microsoft 365 service code has the ability to interpret and traverse the key hierarchy for encryption and decryption activities. Logical isolation exists between the storage locations of Customer Keys, availability keys, other hierarchical keys, and customer data. This isolation mitigates the risk of data exposure in the event one or more locations are compromised. Each layer in the hierarchy has built in 24x7 intrusion detection capabilities to protect data and secrets stored.
-Access controls are implemented to prevent unauthorized access to internal systems, including availability key secret stores. Microsoft engineers don't have direct access to the availability key secret stores. For additional detail on access controls, review [Administrative Access Controls in Microsoft 365](/Office365/securitycompliance/office-365-administrative-access-controls-overview).
+Access controls are implemented to prevent unauthorized access to internal systems, including availability key secret stores. Microsoft engineers don't have direct access to the availability key secret stores. For additional detail on access controls, review [Administrative Access Controls in Microsoft 365](/compliance/office-365-administrative-access-controls-overview).
Technical controls prevent Microsoft personnel from logging into highly-privileged service accounts, which might otherwise be used by attackers to impersonate Microsoft services. For example, these controls prevent interactive logon.
compliance Customer Key Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/customer-key-overview.md
Multi-workload DEPs don't encrypt the following types of data. Instead, Microsof
- SharePoint and OneDrive for Business data. - Microsoft Teams files and some Teams call and meeting recordings saved in OneDrive for Business and SharePoint Online are encrypted using the SharePoint Online DEP. - Other Microsoft 365 workloads such as Yammer and Planner that aren't currently supported by Customer Key.-- Teams Live Events and Q&A in Live Events. For Teams, this scenario is the only one that isn't encrypted by Customer Key using multi-workload DEP.
+- Teams Live Event data.
You can create multiple DEPs per tenant but only assign one DEP at a time. When you assign the DEP, encryption begins automatically but takes some time to complete depending on the size of your tenant.
compliance Export Documents From Review Set https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/export-documents-from-review-set.md
Use the following options to configure the export. Not all options are allowed f
- **Export these documents** - Selected documents only: This option exports only the documents that are currently selected. This option is only available when items are selected in a review set.
+
- All filtered documents: This option exports the documents in an active filter. This option is only available when a filter is applied to the review set.
+
- All documents in the review set: This option exports all documents in the review set. - **Output options**: Exported content is either available for download directly through a web browser or can be sent to an Azure Storage account. The first two options enable direct download. - Reports only: Only the summary and load file are created.
+
- Loose files and PSTs (email is added to PSTs when possible): Files are exported in a format that resembles the original directory structure seen by users in their native applications. For more information, see the [Loose files and PST export structure](#loose-files-and-pst-export-structure) section.
+
- Condensed directory structure: Files are exported and included in the download.
+
- Condensed directory structure exported to your Azure Storage account: Files are exported to your organization's Azure Storage account. For this option, you have to provide the URL for the container in your Azure Storage account to export the files to. You also have to provide the shared access signature (SAS) token for your Azure Storage account. For more information, see [Export documents in a review set to an Azure Storage account](download-export-jobs.md). - **Include**
+
- Tags: When selected, tagging information is included in the load file.
+
- Text files: This option includes the extracted text versions of native files in the export.
+
- Replace redacted natives with converted PDFs: If redacted PDF files are generated during review, these files are available for export. You can choose to export only the native files that were redacted (by not selecting this option) or you can select this option to export the PDF files that contain the actual redactions.
-## The following sections describe the folder structure for loose files and condensed directory structure options
-
-Exports are partitioned into ZIP files with a maximum size of uncompressed content of 75 GB. If the export size is less than 75 GB, the export will consist of a summary file and a single ZIP file. For exports exceeding 75 GB of uncompressed data, multiple ZIP files will be created. Once downloaded, the ZIP files can be uncompressed into a single location to recreate the full export.
+The following sections describe the folder structure for loose files and condensed directory structure options. Exports are partitioned into ZIP files with a maximum size of uncompressed content of 75 GB. If the export size is less than 75 GB, the export will consist of a summary file and a single ZIP file. For exports larger than 75 GB of uncompressed data, multiple ZIP files will be created. Once downloaded, the ZIP files can be uncompressed into a single location to recreate the full export.
### Loose files and PST export structure If you select this export option, the exported content is organized in the following structure: - Summary.csv: Includes a summary of the content exported from the review set+ - Root folder: This folder in named [Export Name] x of z.zip and will be repeated for each ZIP file partition.
+
- Export_load_file_x of z.csv: The metadata file.
+
- Warnings and errors x of z.csv: This file includes information about errors encountered when trying to export from the review set.
+
- Exchange: This folder contains all content from Exchange stored in PST files. Redacted PDF files cannot be included with this option. If an attachment is selected in the review set, the parent email will be exported with the attachment attached.
+
- SharePoint: This folder contains all native content from SharePoint in a native file format. Redacted PDF files cannot be included with this option. ### Condensed directory structure - Summary.csv: Includes a summary of the content exported from the review set+ - Root folder: This folder in named [Export Name] x of z.zip and will be repeated for each ZIP file partition.
+
- Export_load_file_x of z.csv: The metadata file and also includes the location of each file that is stored in the ZIP file.
+
- Warnings and errors x of z.csv: This file includes information about errors encountered when trying to export from the review set.+ - NativeFiles: This folder contains all the native files that were exported. Natives files are replaced with redacted PDFs if you selected the *Replace redacted natives with converted PDFs* option.
+
- Error_files: This folder contains files that had either extraction or other processing error. The files will be placed into separate folders, either ExtractionError or ProcessingError. These files are listed in the load file.+ - Extracted_text_files: This folder contains all of the extracted text files that were generated at processing. ### Condensed directory structure exported to your Azure Storage Account
compliance Importing Pst Files To Office 365 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/importing-pst-files-to-office-365.md
f1.keywords:
Previously updated : Last updated : audience: Admin f1_keywords: - 'ms.o365.cc.IngestionHelp' localization_priority: Priority-+ - Strat_O365_IP - M365-security-compliance search.appverid: MET150
description: Learn how to use the Import service in the Security & Compliance Ce
You can use the Import service in the Security & Compliance Center to quickly bulk-import PST files to Exchange Online mailboxes in your organization. There are two ways you can import PST files to Office 365: -- **Network upload** ![Cloud upload](../media/54ab16ee-3822-4551-abef-3d926f4e1c01.png) - Upload the PST files over the network to a temporary Azure Storage location in the Microsoft cloud. Then you use the Office 365 Import service to import the PST data to mailboxes in your organization.
+- **Network upload** ![Cloud upload](../media/54ab16ee-3822-4551-abef-3d926f4e1c01.png) - Upload the PST files over the network to a temporary Azure Storage location in the Microsoft cloud. Then you use the Office 365 Import service to import the PST data to mailboxes in your organization.
- **Drive shipping** ![Hard disk](../media/e72b76f3-1f73-4296-b749-c325d95d9ef6.png) - Copy the PST files to a BitLocker-encrypted hard drive and then physically ship the drive to Microsoft. When Microsoft receives the hard drive, data center personnel upload the data to a temporary Azure Storage location in the Microsoft cloud. Then you use the Office 365 Import service to import the data to mailboxes in your organization. ## Step-by-step instructions
-
-See one of the following topics for detailed, step-by-step instructions for bulk-importing your organization's PST files to Office 365.
+
+See one of the following topics for detailed, step-by-step instructions for bulk-importing your organization's PST files to Office 365.
- [Use network upload to import PST files to Office 365](use-network-upload-to-import-pst-files.md)
See one of the following topics for detailed, step-by-step instructions for bulk
## How importing PST files works Here's an illustration and description of the complete PST import process. The illustration shows the primary workflow and highlights the differences between the network upload and drive shipping methods.
-
+ ![Workflow of PST import process](../media/76997b69-67d7-433a-a0ca-9389f85a36a1.png)
-
-1. **Download the PST import tools and key to private Azure Storage location** - The first step is to download the tool and access key used to upload the PST files or copy them to a hard drive. You obtain these from the **Import** page in the Security & Compliance Center. The key provides you (or Microsoft data center personnel in the case of drive shipping) with the necessary permissions to upload PST files to a private and secure Azure Storage location. This access key is unique to your organization and helps prevent unauthorized access to your PST files after they're uploaded to the Microsoft cloud. Importing PST files to Microsoft 365 doesn't require your organization to have a separate Azure subscription.
-
+
+1. **Download the PST import tools and key to private Azure Storage location** - The first step is to download the tool and access key used to upload the PST files or copy them to a hard drive. You obtain these from the **Import** page in the Security & Compliance Center. The key provides you (or Microsoft data center personnel in the case of drive shipping) with the necessary permissions to upload PST files to a private and secure Azure Storage location. This access key is unique to your organization and helps prevent unauthorized access to your PST files after they're uploaded to the Microsoft cloud. Importing PST files to Microsoft 365 doesn't require your organization to have a separate Azure subscription.
+ 2. **Upload or copy the PST files** - The next step depends on whether you're using network upload or drive shipping to import PST files. In both cases, you'll use the tool and secure storage key that you obtained in the previous step.
-
+ - **Network upload:** The AzCopy.exe tool (downloaded in step 1) is used to upload and store your PST files in an Azure Storage location in the Microsoft cloud. The Azure Storage location that you upload your PST files to is located in the same regional Microsoft datacenter as your organization.
-
+ To upload them, the PST files that you want to import have to be located in a file share or file server in your organization.
-
+ - **Drive shipping:** The WAImportExport.exe tool (downloaded in step 1) is used to copy your PST files to the hard drive. This tool encrypts the hard drive with BitLocker and then copies the PSTs to the hard drive. Like network upload, the PST files that you want to copy to the hard drive have to be located in a file share or file server in your organization.
-
-3. **Create a PST import mapping file** - After the PST files have been uploaded to the Azure Storage location or copied to a hard drive, the next step is to create a comma-separated value (CSV) file that specifies which user mailboxes the PST files will be imported to (and a PST file can be imported to a user's primary mailbox or their archive mailbox). The Office 365 Import service will use the information to import the PST files.
-
-4. **Create a PST import job** - The next step is to create a PST import job on the **Import PST files** page in the Security & Compliance Center and submit the PST import mapping file created in the previous step. For network upload (because the PST files have been uploaded to Azure) Microsoft 365 analyzes the data in the PST files and then gives you an opportunity to set filters that control what data actually gets imported to the mailboxes specified in the PST import mapping file.
-
+
+3. **Create a PST import mapping file** - After the PST files have been uploaded to the Azure Storage location or copied to a hard drive, the next step is to create a comma-separated value (CSV) file that specifies which user mailboxes the PST files will be imported to (and a PST file can be imported to a user's primary mailbox or their archive mailbox). The Office 365 Import service will use the information to import the PST files.
+
+4. **Create a PST import job** - The next step is to create a PST import job on the **Import PST files** page in the Security & Compliance Center and submit the PST import mapping file created in the previous step. For network upload (because the PST files have been uploaded to Azure) Microsoft 365 analyzes the data in the PST files and then gives you an opportunity to set filters that control what data actually gets imported to the mailboxes specified in the PST import mapping file.
+ For drive shipping, a few other things happen at this point in the process.
-
+ - You physically ship the hard drive to a Microsoft data center (the shipping address for the Microsoft data center is displayed when the import job is created).
-
+ - When Microsoft receives the hard drive, data center personnel will upload the PST files on the hard drive to the Azure Storage location for your organization. As previously explained, your PST files are uploaded to an Azure Storage location that resides in the same regional Microsoft datacenter where your organization is located.
-
+ > [!NOTE] > The PST files on the hard drive are uploaded to Azure within 7 to 10 business days after Microsoft receives the hard drive. Like the network upload process, Microsoft 365 then analyzes the data in the PST files and gives you an opportunity to set filters that control what data actually gets imported to the mailboxes specified in the PST import mapping file.
-
+ - Microsoft ships the hard drive back to you.
-
-5. **Filter the PST data that will be imported to mailboxes** - After the import job is created (and after the PST files from a drive shipping job are uploaded to the Azure Storage location) Microsoft 365 analyzes the data in the PST files (safely and securely) by identifying the age of the items and the different message types included in the PST files. When the analysis is completed and the data is ready to import, you have the option to import all the data contained in the PST files or you can trim the data that's imported by setting filters that control what data gets imported.
-
+
+5. **Filter the PST data that will be imported to mailboxes** - After the import job is created (and after the PST files from a drive shipping job are uploaded to the Azure Storage location) Microsoft 365 analyzes the data in the PST files (safely and securely) by identifying the age of the items and the different message types included in the PST files. When the analysis is completed and the data is ready to import, you have the option to import all the data contained in the PST files or you can trim the data that's imported by setting filters that control what data gets imported.
+ 6. **Start the PST import job** - After the import job is started, Microsoft 365 uses the information in the PST import mapping file to import the PSTs files from the he Azure Storage location to user mailboxes. Status information about the import job (including information about each PST file being imported) is displayed on the **Import PST files** page in the Security & Compliance Center. When the import job is finished, the status for the job is set to **Complete**.
-
+ ## Why import email data to Microsoft 365? - It's a good way to import your organization's archival messaging data to Microsoft 365.
-
-- You can use the [Intelligent Import](filter-data-when-importing-pst-files.md) feature to filter the items in PST files that actually get imported to the target mailboxes. This lets you trim the data that's imported by setting filters that control what data gets imported.
-
+
+- You can use the [Intelligent Import](filter-data-when-importing-pst-files.md) feature to filter the items in PST files that actually get imported to the target mailboxes. This lets you trim the data that's imported by setting filters that control what data gets imported.
+ - Importing email data to Microsoft 365 helps address compliance needs of your organization by letting you:
-
- - Enable [archive mailboxes](enable-archive-mailboxes.md) and [unlimited archiving](unlimited-archiving.md) to give users additional mailbox storage space.
-
- - Place mailboxes on [Litigation Hold](./create-a-litigation-hold.md) to retain content.
-
- - Use the [Content Search tool](content-search.md) to search for mailbox content.
-
- - Use [eDiscovery cases](./get-started-core-ediscovery.md) to manage your organization's legal investigations
-
- - Use [retention policies](retention.md) in the Security & Compliance Center to control how long mailbox content is retained, and then delete content after the retention period expires.
+
+ - Enable [archive mailboxes](enable-archive-mailboxes.md) and [unlimited archiving](unlimited-archiving.md) to give users additional mailbox storage space.
+
+ - Place mailboxes on [Litigation Hold](./create-a-litigation-hold.md) to retain content.
+
+ - Use the [Content Search tool](content-search.md) to search for mailbox content.
+
+ - Use [eDiscovery cases](./get-started-core-ediscovery.md) to manage your organization's legal investigations
+
+ - Use [retention policies](retention.md) in the Security & Compliance Center to control how long mailbox content is retained, and then delete content after the retention period expires.
- Use [Communication compliance policies](communication-compliance.md) to examine messages to make sure they are compliant with message standards and add a classification type.
-
+ - Importing data to Microsoft 365 helps protect against data loss. Email data that's imported to Microsoft 365 inherits the high availability features of Exchange Online.
-
+ - Email data is available to users from all devices because it's stored in the cloud.
-
+ ## Importing SharePoint data to Microsoft 365 You can also import files and documents to SharePoint sites and OneDrive accounts in your organization. For more information, see the following articles:
You can also import files and documents to SharePoint sites and OneDrive account
- [Migrate your file share content to SharePoint Online using the Azure Data Box](/sharepointmigration/how-to-migrate-file-share-content-to-spo-using-azuredatabox) ## Frequently asked questions about importing PST files
-
-Here are some frequently asked questions about using the Office 365 Import service to bulk-import PST files to Microsoft 365 mailboxes.
-
+
+Here are some frequently asked questions about using the Office 365 Import service to bulk-import PST files to Microsoft 365 mailboxes.
+ - [Using network upload to import PST files](#using-network-upload-to-import-pst-files)
-
+ - [Using drive shipping to import PST files](#using-drive-shipping-to-import-pst-files)
-
+ ### Using network upload to import PST files **What permissions are required to create import jobs in the Office 365 Import Service?**
-
+ You have to be assigned the Mailbox Import Export role in Exchange Online to import PST files to Microsoft 365 mailboxes. By default, this role isn't assigned to any role group in Exchange Online. You can add the Mailbox Import Export role to the Organization Management role group. Or you can create a new role group, assign the Mailbox Import Export role, and then add yourself or other users as a member. For more information, see the "Add a role to a role group" or the "Create a role group" sections in [Manage role groups in Exchange Online](/Exchange/permissions-exo/role-groups).
-
+ Additionally, to create import jobs in the Security & Compliance Center, one of the following must be true:
-
+ - You have to be assigned the Mail Recipients role in Exchange Online. By default, this role is assigned to the Organization Management and Recipient Management roles groups. Or
-
+ - You have to be a global administrator in your organization. > [!TIP]
-> Consider creating a new role group in Exchange Online that's specifically intended for importing PST files to Office 365. For the minimum level of privileges required to import PST files, assign the Mailbox Import Export and Mail Recipients roles to the new role group, and then add members.
-
+> Consider creating a new role group in Exchange Online that's specifically intended for importing PST files to Office 365. For the minimum level of privileges required to import PST files, assign the Mailbox Import Export and Mail Recipients roles to the new role group, and then add members.
+ **Where is network upload available?**
-
+ Network upload is currently available in these regions: United States, Canada, Brazil, the United Kingdom, France, Germany, Switzerland, Norway, Europe, India, East Asia, Southeast Asia, Japan, Republic of Korea, Australia, and United Arab Emirates (UAE). Network upload will be available in more regions soon.
-
+ **What is the pricing for importing PST files by using network upload?**
-
+ Using network upload to import PST files is free.
-
+ This also means that after PST files are deleted from the Azure Storage area, they're no longer displayed in the list of files for a completed import job in the Microsoft 365 admin center. Although an import job might still be listed on the **Import data to Office 365** page, the list of PST files might be empty when you view the details of older import jobs.
-
+ **What version of the PST file format is supported for importing to Office 365?**
-
+ There are two versions of the PST file format: ANSI and Unicode. We recommend importing files that use the Unicode PST file format. However, files that use the ANSI PST file format, such as those for languages that use a double-byte character set (DBCS), can also be imported to Office 365. For more information about importing ANSI PST files, see Step 4 in [Use network upload to import PST files to Office 365](./use-network-upload-to-import-pst-files.md).
-
+ Additionally, PST files from Outlook 2007 and later versions can be imported to Office 365.
-
+ **After I upload my PST files to the Azure Storage area, how long are they kept in Azure before they're deleted?**
-
+ When you use the network upload method to import PST files, you upload them to an Azure blob container named `ingestiondata`. If there are no import jobs in progress on the **Import PST files** page in the Security & Compliance Center), then all PST files in the `ingestiondata` container in Azure are deleted 30 days after the most recent import job was created in the Security & Compliance Center. That also means you have to create a new import job in the Security & Compliance Center (described in Step 5 in the network upload instructions) within 30 days of uploading PST files to Azure.
-
+ This also means that after PST files are deleted from the Azure Storage area, they're no longer displayed in the list of files for a completed import job in the Security & Compliance Center. Although an import job might still be listed on the **Import PST files** page in the Security & Compliance Center, the list of PST files might be empty when you view the details of older import jobs.
-
+ **How long does it take to import a PST file to a mailbox?**
-
-It depends on the capacity of your network, but it typically takes several hours for each terabyte (TB) of data to be uploaded to the Azure Storage area for your organization. After the PST files are copied to the Azure Storage area, a PST file is imported to a Microsoft 365 mailbox at a rate of at least 24 GB per day. If this rate doesn't meet your needs, you might consider other methods to get email data into Office 365. For more information, see [Ways to migrate multiple email accounts to Office 365](/Exchange/mailbox-migration/mailbox-migration).
-
-If different PST files are imported to different target mailboxes, the import process occurs in parallel; in other words, each PST/mailbox pair is imported simultaneously. Likewise, if multiple PST files are imported to the same mailbox, they will be simultaneously imported.
-
+
+It depends on the capacity of your network, but it typically takes several hours for each terabyte (TB) of data to be uploaded to the Azure Storage area for your organization. After the PST files are copied to the Azure Storage area, a PST file is imported to a Microsoft 365 mailbox at a rate of approximately 24 GB per day<sup>\*</sup>. If this rate doesn't meet your needs, you might consider other methods to get email data into Office 365. For more information, see [Ways to migrate multiple email accounts to Office 365](/Exchange/mailbox-migration/mailbox-migration).
+
+<sup>\*</sup> This rate is not guaranteed. Server workload and transient performance issues might decrease this rate.
+
+If different PST files are imported to different target mailboxes, the import process occurs sequentially (one at a time) and throttling occurs.
+ **How does the PST import process handle duplicate email items?** The PST import process checks for duplicate items and doesn't copy the items from a PST file to the mailbox or archive if a matching item exists in the target folder in the target mailbox or target archive. If you reimport the same PST file and specify a different target folder (using the TargetRootFolder property in the PST import mapping file) than the one you specified in a previous import job, all items in the PST file will be reimported.
-
+ **Is there a message size limit when importing PST files?**
-
+ Yes. If a PST file contains a mailbox item that is larger than 150 MB, the item will be skipped and not imported during the import process. Items larger than 150 MB aren't imported because 150 MB is the message size limit in Exchange Online. For more information, see [Message limits in Exchange Online](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#message-limits).
-
+ **Are message properties, such as when the message was sent or received, the list of recipients and other properties, preserved when PST files are imported to a Microsoft 365 mailbox?**
-
+ Yes. The original message metadata isn't changed during the import process.
-
+ **Is there a limit to the number of levels in a folder hierarchy for a PST file that I want to import to a mailbox?**
-
+ Yes. You can't import a PST file that has 300 or more levels of nested folders.
-
+ **Can I use network upload to import PST files to an inactive mailbox in Office 365?**
-
+ Yes, this capability is now available.
-
+ **Can I use network upload to import PST files to an online archive mailbox in an Exchange hybrid deployment?**
-
+ Yes, this capability is now available.
-
+ **Can I use network upload to import PST files to public folders in Exchange Online?**
-
+ No, you can't import PST files to public folders.
-
+ ### Using drive shipping to import PST files **What permissions are required to create import jobs in the Office 365 Import Service?**
-
+ You have to be assigned the Mailbox Import Export role to import PST files to Microsoft 365 mailboxes. By default, this role isn't assigned to any role group in Exchange Online. You can add the Mailbox Import Export role to the Organization Management role group. Or you can create a new role group, assign the Mailbox Import Export role, and then add yourself or other users as a member. For more information, see the "Add a role to a role group" or the "Create a role group" sections in [Manage role groups in Exchange Online](/Exchange/permissions-exo/role-groups).
-
+ Additionally, to create import jobs in the Security & Compliance Center, one of the following must be true:
-
+ - You have to be assigned the Mail Recipients role in Exchange Online. By default, this role is assigned to the Organization Management and Recipient Management roles groups.
-
+ Or
-
+ - You have to be a global administrator in your organization.
-
+ > [!TIP]
-> Consider creating a new role group in Exchange Online that's specifically intended for importing PST files to Office 365. For the minimum level of privileges required to import PST files, assign the Mailbox Import Export and Mail Recipients roles to the new role group, and then add members.
-
+> Consider creating a new role group in Exchange Online that's specifically intended for importing PST files to Office 365. For the minimum level of privileges required to import PST files, assign the Mailbox Import Export and Mail Recipients roles to the new role group, and then add members.
+ **Where is drive shipping available?**
-
+ Drive shipping is currently available in the United States, Canada, Brazil, the United Kingdom, Europe, India, East Asia, Southeast Asia, Japan, Republic of Korea, and Australia. Drive shipping will be available in more regions soon. > [!NOTE] > At this time, drive shipping to import PST files is not available in Germany and Switzerland. This FAQ will be updated when drive shipping is available in these countries.
-
+ **What commercial licensing agreements support drive shipping?**
-
+ Drive shipping to import PST files to Microsoft 365 is available through a Microsoft Enterprise Agreement (EA). Drive shipping isn't available through a Microsoft Products and Services Agreement (MPSA).
-
+ **What is the pricing for using drive shipping to import PST files to Microsoft 365?**
-
+ The cost to use drive shipping to import PST files to Microsoft 365 mailboxes is $2 USD per GB of data. For example, if you ship a hard drive that contains 1,000 GB (1 TB) of PST files, the cost is $2,000 USD. You can work with a partner to pay the import fee. For information about finding a partner, see [Find your Microsoft partner or reseller](../admin/manage/find-your-partner-or-reseller.md).
-
+ **What kind of hard drives are supported for drive shipping?**
-
+ Only 2.5-inch solid-state drives (SSDs) or 2.5 inch or 3.5 inch SATA II/III internal hard drives are supported for use with the Office 365 Import service. You can use hard drives up to 10 TB. For import jobs, only the first data volume on the hard drive will be processed. The data volume must be formatted with NTFS. When copying data to a hard drive, you can attach it directly using a 2.5 inch SSD or 2.5 inch or 3.5 inch SATA II/III connector or you can attach it externally using an external 2.5 inch SSD or 2.5 inch or 3.5 inch SATA II/III USB adaptor.
-
+ > [!IMPORTANT]
-> External hard drives that come with an built-in USB adaptor aren't supported by the Office 365 Import service. Additionally, the disk inside the casing of an external hard drive can't be used. Please don't ship external hard drives.
-
+> External hard drives that come with an built-in USB adaptor aren't supported by the Office 365 Import service. Additionally, the disk inside the casing of an external hard drive can't be used. Please don't ship external hard drives.
+ **How many hard drives can I ship for a single import job?**
-
+ You can ship a maximum of 10 hard drives for a single import job.
-
+ **After I ship my hard drive, how long does it take to get to the Microsoft datacenter?**
-
+ That depends on a few things, such as your proximity to the Microsoft data center and what kind of shipping option you used to ship your hard drive (such as, next-day delivery, two-day delivery, or ground-delivery). With most shippers, you can use the tracking number to track the status of your delivery.
-
+ **After my hard drive arrives at the Microsoft datacenter, how long does it take to upload my PST files to Azure?**
-
-After your hard drive is received at the Microsoft data center, it will take between 7 to 10 business days to upload the PST files to the Azure Storage location for your organization. The PST files will be uploaded to an Azure blob container named `ingestiondata`.
-
+
+After your hard drive is received at the Microsoft data center, it will take between 7 to 10 business days to upload the PST files to the Azure Storage location for your organization. The PST files will be uploaded to an Azure blob container named `ingestiondata`.
+ **How long does it take to import a PST file to a mailbox?**
-
+ After the PST files are uploaded to the Azure Storage area, Microsoft 365 analyzes the data in the PST files (in a safe and secure manner) to identify the age of the items and the different message types included in the PST files. When this analysis is complete, you'll have the option to import all the data in the PST files or set filters to that control what data gets imported. After you start the import job, a PST file is imported to a Microsoft 365 mailbox at a rate of at least 24 GB per day. If this rate doesn't meet your needs, you might consider other methods to get email data into Microsoft 365. For more information, see [Ways to migrate multiple email accounts to Microsoft 365](/Exchange/mailbox-migration/mailbox-migration).
-
+ If different PST files are imported to different target mailboxes, the import process occurs in parallel; in other words, each PST/mailbox pair is imported simultaneously. Likewise, if multiple PST files are imported to the same mailbox, they will be simultaneously imported.
-
+ **After Microsoft uploads my PST files to Azure, how long are they kept in Azure before they're deleted?**
-
-All PST files in the Azure Storage location for your organization (in blob container named `ingestiondata`), are deleted 30 days after the most recent import job was created on the **Import PST files** page in the Security & Compliance Center.
-
-This also means that after PST files are deleted from the Azure Storage area, they're no longer displayed in the list of files for a completed import job in the Security & Compliance Center. Although an import job might still be listed on the **Import PST files** page in the Security & Compliance Center, the list of PST files might be empty when you view the details of older import jobs.
-
+
+All PST files in the Azure Storage location for your organization (in blob container named `ingestiondata`), are deleted 30 days after the most recent import job was created on the **Import PST files** page in the Security & Compliance Center.
+
+This also means that after PST files are deleted from the Azure Storage area, they're no longer displayed in the list of files for a completed import job in the Security & Compliance Center. Although an import job might still be listed on the **Import PST files** page in the Security & Compliance Center, the list of PST files might be empty when you view the details of older import jobs.
+ **What version of the PST file format is supported for importing to Microsoft 365?**
-
+ There are two versions of the PST file format: ANSI and Unicode. We recommend importing files that use the Unicode PST file format. However, files that use the ANSI PST file format, such as those for languages that use a double-byte character set (DBCS), can also be imported to Microsoft 365. For more information about importing ANSI PST files, see Step 3 in [Use drive shipping to import your organization PST files to Microsoft 365](use-drive-shipping-to-import-pst-files-to-office-365.md#step-3-create-the-pst-import-mapping-file).
-
+ Additionally, PST files from Outlook 2007 and later versions can be imported to Microsoft 365.
-
+ **Is there a message size limit when importing PST files?**
-
+ Yes. If a PST file contains a mailbox item that is larger than 150 MB, the item will be skipped and not imported during the import process. Items larger than 150 MB aren't imported because 150 MB is the message size limit in Exchange Online. For more information, see [Message limits in Exchange Online](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#message-limits).
-
+ **How does the PST import process handle duplicate email items?** The PST import process checks for duplicate items and doesn't copy the items from a PST file to the mailbox or archive if a matching item exists in the target folder in the target mailbox or target archive. If you reimport the same PST file and specify a different target folder (using the TargetRootFolder property in the PST import mapping file) than the one you specified in a previous import job, all items in the PST file will be reimported.
-
+ **Are message properties, such as when the message was sent or received, the list of recipients and other properties, preserved when PST files are imported to a Microsoft 365 mailbox?**
-
+ Yes. The original message metadata isn't changed during the import process
-
+ **Is there a limit to the number of levels in a folder hierarchy for a PST file that I want to import to a mailbox?**
-
+ Yes. You can't import a PST file that has 300 or more levels of nested folders.
-
+ **Can I use drive shipping to import PST files to an inactive mailbox in Microsoft 365?**
-
+ Yes, this capability is now available.
-
+ **Can I use drive shipping to import PST files to an online archive mailbox in an Exchange hybrid deployment?**
-
+ Yes, this capability is now available.
-
+ **Can I use drive shipping to import PST files to public folders in Exchange Online?**
-
+ No, you can't import PST files to public folders.
-
+ **Can Microsoft wipe my hard drive before they ship it back to me?**
-
+ No, Microsoft can't wipe hard drives before shipping them back to customers. Hard drives are returned to you in the same state they were in when they were received by Microsoft.
-
+ **Can Microsoft shred my hard drive instead of shipping it back to me?**
-
+ No, Microsoft can't destroy your hard drive. Hard drives are returned to you in the same state they were in when they were received by Microsoft.
-
+ **What courier services are supported for return shipping?**
-
+ If you're a customer in the United States or Europe, Microsoft uses FedEx to return your hard drive. For all other regions, Microsoft uses DHL.
-
+ **What are the return shipping costs?**
-
+ Return shipping costs vary, depending on your proximity to the Microsoft data center that you shipped your hard drive to. Microsoft will bill your FedEx or DHL account to return your hard drive. The cost of return shipping is your responsibility.
-
+ **Can I use a custom courier shipping service, such as FedEx Custom Shipping, to ship my hard drive to Microsoft?**
-
+ Yes.
-
+ **If I have to ship my hard drive to another country, is there anything I need to do?**
-
-The hard drive that you ship to Microsoft might have to cross international borders. If so, you're responsible for ensuring that the hard drive and the data it contains are imported and/or exported in accordance with the applicable laws. Before shipping a hard drive, check with your advisors to verify that your drive and data can legally be shipped to the specified Microsoft data center. This will help to ensure that it reaches Microsoft in a timely manner.
+
+The hard drive that you ship to Microsoft might have to cross international borders. If so, you're responsible for ensuring that the hard drive and the data it contains are imported and/or exported in accordance with the applicable laws. Before shipping a hard drive, check with your advisors to verify that your drive and data can legally be shipped to the specified Microsoft data center. This will help to ensure that it reaches Microsoft in a timely manner.
compliance Limits For Content Search https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/limits-for-content-search.md
audience: Admin
localization_priority: Normal-+ - Strat_O365_IP - M365-security-compliance
+search.appverid:
- MOE150 - MET150 ms.assetid: 78fe3147-1979-4c41-83bb-aeccf244368d description: "Learn about the limits in effect for the Content search and Core eDiscovery features in the Microsoft 365 compliance center."
-# Limits for eDiscovery search
+# Limits for eDiscovery search
Various limits are applied to eDiscovery search tools in the Microsoft 365 compliance center. This includes searches run on the **Content search** page and searches that are associated with an eDiscovery case on the **Core eDiscovery** page. These limits help to maintain the health and quality of services provided to organizations. There are also limits related to the indexing of email messages in Exchange Online for search. You can't modify the limits for eDiscovery searches or email indexing, but you should be aware of them so that you can take these limits into consideration when planning, running, and troubleshooting eDiscovery searches. For limits related to the Advanced eDiscovery tool, see [Limits in Advanced eDiscovery](limits-ediscovery20.md)
-
+ ## Search limits The following table lists the search limits when using the content search tool in the Microsoft 365 compliance center and for searches that are associated with a Core eDiscovery case.
-
-| Description of limit | Limit |
-|:--|:--|
-|The maximum number of mailboxes or sites that can be searched in a single search <br/> |No limit <sup>1</sup> <br/> |
-|The maximum number of searches that can run at the same time in your organization. <br/> |30 <br/> |
-|The maximum number of organization-wide searches that can be run at the same time. <br/> |3 <br/> |
-|The maximum number of searches that a single user can start at the same time. This limit is most likely hit when the user tries to start multiple searches by using the **Get-ComplianceSearch \| Start-ComplianceSearch** command in Security & Compliance Center PowerShell. <br/> |10 <br/> |
-|The maximum number of items per user mailbox that are displayed on the preview page when previewing Content Search results. <br/> |100 <br/> |
-|The maximum number of items found in all user mailboxes that are displayed on the preview page when previewing search results. The newest items are displayed. <br/> |1,000 <br/> |
-|The maximum number of user mailboxes that can be previewed for search results. If there are more than 1000 mailboxes that contain content that matches the search query, only the top 1000 mailboxes with the most search results will be available for preview. <br/> |1,000 <br/> |
-|The maximum number of items found in SharePoint and OneDrive for Business sites that are displayed on the preview page when previewing search results. The newest items are displayed. <br/> |200 <br/> |
-|The maximum number of sites (in SharePoint and OneDrive for Business) that can be previewed for search results. If there are more than 200 total sites that contain content that matches the search query, only the top 200 sites with the most search results will be available for preview. <br/> |200 <br/> |
-|The maximum number of items per public folder mailbox that are displayed on the preview page when previewing content search results. <br/> |100 <br/> |
-|The maximum number of items found in all public folder mailboxes that are displayed on the preview page when previewing content search results. <br/> |200 <br/> |
-|The maximum number of public folder mailboxes that can be previewed for search results. If there are more than 500 public folder mailboxes that contain content that matches the search query, only the top 500 public folder mailboxes with the most search results will be available for preview. <br/> |500 <br/> |
-|The maximum number of characters for the search query (including operators and conditions) for a search. <br/><br/> **Note:** This limit takes effect after the query is expanded and includes characters from the keyword query, any search permissions filters applied to the user, and the URLs of all site locations. This means the query will get expanded against each of the keywords. For example, if a search query has 15 keywords and additional parameters and conditions, the query gets expanded 15 times, each with the other parameters and conditions in the query. So even though the number of characters in the search query may be below the limit, it's the expanded query that may contribute to exceeding this limit. <br/> |**Mailboxes:** 10,000 <br/> **Sites:** 4,000 when searching all sites or 2,000 when searching up to 20 sites <sup>2</sup> <br/> |
-|Maximum number of variants returned when using a prefix wildcard to search for an exact phrase in a search query or when using a prefix wildcard and the **NEAR** Boolean operator. <br/> |10,000 <sup>3</sup> <br/> |
-|The minimum number of alpha characters for prefix wildcards; for example, `time*`, `one*`, or `set*`. <br/> |3 <br/> |
-|The maximum number of mailboxes in a search that you can delete items in by doing a "search and purge" action (by using the **New-ComplianceSearchAction -Purge** command). If the search that you're doing a purge action for has more source mailboxes than this limit, the purge action will fail. For more information about search and purge, see [Search for and delete email messages in your organization](search-for-and-delete-messages-in-your-organization.md). <br/> |50,000 <br/> |
-|The maximum number of locations in a search that you can export items from. If the search that you're exporting has more locations than this limit, the export will fail. For more information, see [Export content search results](export-search-results.md). <br/> |100,000 <br/> |
+
+<br>
+
+****
+
+|Description of limit|Limit|
+|||
+|The maximum number of mailboxes or sites that can be searched in a single search|No limit <sup>1</sup>|
+|The maximum number of searches that can run at the same time in your organization.|30|
+|The maximum number of organization-wide searches that can be run at the same time.|3|
+|The maximum number of searches that a single user can start at the same time. This limit is most likely hit when the user tries to start multiple searches by using the **Get-ComplianceSearch \|Start-ComplianceSearch** command in Security & Compliance Center PowerShell.|10|
+|The maximum number of items per user mailbox that are displayed on the preview page when previewing Content Search results.|100|
+|The maximum number of items found in all user mailboxes that can possibly be displayed on the preview page when previewing search results. The newest items are displayed.|1,000 <sup>2</sup>|
+|The maximum number of user mailboxes that can be previewed for search results. If there are more than 1000 mailboxes that contain content that matches the search query, at most, only the top 1000 mailboxes with the most search results will be available for preview.|1,000|
+|The maximum number of items found in SharePoint and OneDrive for Business sites that are displayed on the preview page when previewing search results. The newest items are displayed.|200|
+|The maximum number of sites (in SharePoint and OneDrive for Business) that can be previewed for search results. If there are more than 200 total sites that contain content that matches the search query, only the top 200 sites with the most search results will be available for preview.|200|
+|The maximum number of items per public folder mailbox that are displayed on the preview page when previewing content search results.|100|
+|The maximum number of items found in all public folder mailboxes that are displayed on the preview page when previewing content search results.|200|
+|The maximum number of public folder mailboxes that can be previewed for search results. If there are more than 500 public folder mailboxes that contain content that matches the search query, only the top 500 public folder mailboxes with the most search results will be available for preview.|500|
+|The maximum number of characters for the search query (including operators and conditions) for a search. <p> **Note:** This limit takes effect after the query is expanded and includes characters from the keyword query, any search permissions filters applied to the user, and the URLs of all site locations. This means the query will get expanded against each of the keywords. For example, if a search query has 15 keywords and additional parameters and conditions, the query gets expanded 15 times, each with the other parameters and conditions in the query. So even though the number of characters in the search query may be below the limit, it's the expanded query that may contribute to exceeding this limit.|**Mailboxes:** 10,000. <p> **Sites:** 4,000 when searching all sites or 2,000 when searching up to 20 sites. <sup>3</sup>|
+|Maximum number of variants returned when using a prefix wildcard to search for an exact phrase in a search query or when using a prefix wildcard and the **NEAR** Boolean operator.|10,000 <sup>4</sup>|
+|The minimum number of alpha characters for prefix wildcards; for example, `time*`, `one*`, or `set*`.|3|
+|The maximum number of mailboxes in a search that you can delete items in by doing a "search and purge" action (by using the **New-ComplianceSearchAction -Purge** command). If the search that you're doing a purge action for has more source mailboxes than this limit, the purge action will fail. For more information about search and purge, see [Search for and delete email messages in your organization](search-for-and-delete-messages-in-your-organization.md).|50,000|
+|The maximum number of locations in a search that you can export items from. If the search that you're exporting has more locations than this limit, the export will fail. For more information, see [Export content search results](export-search-results.md).|100,000|
||| > [!NOTE]
-> <sup>1</sup> Although you can search an unlimited number of mailboxes in a single search, you can only download the exported search results from a maximum of 100,000 mailboxes using the eDiscovery Export Tool in the Microsoft 365 compliance center. <br/><br/> <sup>2</sup> When searching SharePoint and OneDrive for Business locations, the characters in the URLs of the sites being searched are counted against this limit. <br/><br/> <sup>3</sup> For non-phrase queries (a keyword value that doesn't use double quotation marks) we use a special prefix index. This tells us that a word occurs in a document, but not where it occurs in the document. To do a phrase query (a keyword value with double quotation marks), we need to compare the position within the document for the words in the phrase. This means that we can't use the prefix index for phrase queries. In this case, we internally expand the query with all possible words that the prefix expands to; for example, `"time*"` can expand to `"time OR timer OR times OR timex OR timeboxed OR …"`. 10,000 is the maximum number of variants the word can expand to, not the number of documents matching the query. There is no upper limit for non-phrase terms.
-
+> <sup>1</sup> Although you can search an unlimited number of mailboxes in a single search, you can only download the exported search results from a maximum of 100,000 mailboxes using the eDiscovery Export Tool in the Microsoft 365 compliance center.
+>
+> <sup>2</sup> The intent of the preview page is to show a limited sample of the results. Even for massive searches with thousands of results, the number of items that are shown on the preview page can, and often will, be much less than maximum possible value of 1000. To see the complete search results, you need to export the results.
+>
+> <sup>3</sup> When searching SharePoint and OneDrive for Business locations, the characters in the URLs of the sites being searched are counted against this limit.
+>
+> <sup>4</sup> For non-phrase queries (a keyword value that doesn't use double quotation marks) we use a special prefix index. This tells us that a word occurs in a document, but not where it occurs in the document. To do a phrase query (a keyword value with double quotation marks), we need to compare the position within the document for the words in the phrase. This means that we can't use the prefix index for phrase queries. In this case, we internally expand the query with all possible words that the prefix expands to; for example, `"time*"` can expand to `"time OR timer OR times OR timex OR timeboxed OR ..."`. 10,000 is the maximum number of variants the word can expand to, not the number of documents matching the query. There is no upper limit for non-phrase terms.
+ ## Search times+ Microsoft collects performance information for searches run by all organizations. While the complexity of the search query can impact search times, the biggest factor that affects how long searches take is the number of mailboxes searched. Although Microsoft doesn't provide a Service Level Agreement for search times, the following table lists average search times for collection searches based on the number of mailboxes included in the search.
+<br>
+
+****
+ |Number of mailboxes|Average search time|
-|:--|:--|
+|||
|100|30 seconds| |1,000|45 seconds| |10,000|4 minutes|
Microsoft collects performance information for searches run by all organizations
||| ## Export limits+ The following table lists the limits when exporting the results of a content search. These limits also apply when you export content from a Core eDiscovery case.
+<br>
+
+****
+ |Description of limit|Limit|
-|:--|:--|
-|Maximum amount of exportable data from a single search <br/><br/> **Note:** If the search results are larger than 2 TB, consider using date ranges or other types of filters to decrease the total size of the search results. <br/> |2 TB <br/> |
-|Maximum an organization can export in a single day <br/><br/> **Note:** This limit is reset daily at 12:00AM UTC <br/> |2 TB <br/> |
-|Maximum concurrent exports that can be ran at same time within your organization <br/><br/> **Note:** Running a **Report Only** export counts against total concurrent exports for your organization. If three users are performing 3 exports each, then only one other export can be performed. Whether it is exporting a report or search results, no other exports can be performed until one has completed. <br/> |10 <br/> |
-|Maximum exports a single user can run at any one time <br/> |3 <br/> |
-|Maximum number of mailboxes for search results that can be downloaded using the eDiscovery Export Tool <br/>| 100,000 <br/>|
-|Maximum size of PST file that can be exported <br/><br/> **Note:** If the search results from a user's mailbox are larger than 10 GB, the search results for the mailbox will be exported in two (or more) separate PST files. If you choose to export all search results in a single PST file, the PST file will be spilt into additional PST files if the total size of the search results is larger than 10 GB. If you want to change this default size, you can edit the Windows Registry on the computer that you use to export the search results. See [Change the size of PST files when exporting eDiscovery search results](change-the-size-of-pst-files-when-exporting-results.md). The search results from a specific mailbox won't be divided among multiple PST files unless the content from a single mailbox is more than 10 GB. If you chose to export the search results in one PST file for that contains all messages in a single folder and the search results are larger than 10 GB, the items are still organized in chronological order, so they will be spilt into additional PST files based on the sent date.<br/> | 10 GB <br/> |
-|Rate at which search results from mailboxes and sites are uploaded to a Microsoft-provided Azure Storage location. |Maximum of 2 GB per hour|
+|||
+|Maximum amount of exportable data from a single search <p> **Note:** If the search results are larger than 2 TB, consider using date ranges or other types of filters to decrease the total size of the search results.|2 TB|
+|Maximum an organization can export in a single day <p> **Note:** This limit is reset daily at 12:00AM UTC|2 TB|
+|Maximum concurrent exports that can be ran at same time within your organization <p> **Note:** Running a **Report Only** export counts against total concurrent exports for your organization. If three users are performing 3 exports each, then only one other export can be performed. Whether it is exporting a report or search results, no other exports can be performed until one has completed.|10|
+|Maximum exports a single user can run at any one time|3|
+|Maximum number of mailboxes for search results that can be downloaded using the eDiscovery Export Tool|100,000|
+|Maximum size of PST file that can be exported <p> **Note:** If the search results from a user's mailbox are larger than 10 GB, the search results for the mailbox will be exported in two (or more) separate PST files. If you choose to export all search results in a single PST file, the PST file will be spilt into additional PST files if the total size of the search results is larger than 10 GB. If you want to change this default size, you can edit the Windows Registry on the computer that you use to export the search results. See [Change the size of PST files when exporting eDiscovery search results](change-the-size-of-pst-files-when-exporting-results.md). The search results from a specific mailbox won't be divided among multiple PST files unless the content from a single mailbox is more than 10 GB. If you chose to export the search results in one PST file for that contains all messages in a single folder and the search results are larger than 10 GB, the items are still organized in chronological order, so they will be spilt into additional PST files based on the sent date.|10 GB|
+|Rate at which search results from mailboxes and sites are uploaded to a Microsoft-provided Azure Storage location.|Maximum of 2 GB per hour|
||| ## Indexing limits for email messages The following table describes the indexing limits that might result in an email message being returned as an unindexed item or a partially indexed item in the results of a content search.
-
-| Indexing limit | Maximum value | Description |
-|:--|:--|:--|
-|Maximum attachment size|150 MB <br/> |The maximum size of an email attachment that will parse for indexing. Any attachment that's larger than this limit won't be parsed for indexing, and the message with the attachment will be marked as partially indexed. <br/> <br/>**Note:** Parsing is the process where the indexing service extracts text from the attachment, removes unnecessary characters like punctuation and spaces, and then divides the text into words (in a process called tokenization), that are then stored in the index. |
-|Maximum number of attachments <br/> |250 <br/> |The maximum number of files attached to an email message that will be parsed for indexing. If a message has more than 250 attachments, the first 250 attachments are parsed and indexed, and the message is marked as partially indexed because it had additional attachments that weren't parsed. <br/> |
-|Maximum attachment depth <br/> |30 <br/> |The maximum number of nested attachments that are parsed. For example, if an email message has another message attached to it and the attached message has an attached Word document, the Word document and the attached message will be indexed. This behavior will continue for up to 30 nested attachments. <br/> |
-|Maximum number of attached images <br/> |0 <br/> |An image that's attached to an email message is skipped by the parser and isn't indexed. <br/> |
-|Maximum time spent parsing an item <br/> |30 seconds <br/> |A maximum of 30 seconds is spent parsing an item for indexing. If the parsing time exceeds 30 seconds, the item is marked as partially indexed. <br/> |
-|Maximum parser output <br/> |2 million characters <br/> |The maximum amount of text output from the parser that's indexed. For example, if the parser extracted 8 million characters from a document, only the first 2 million characters are indexed. <br/> |
-|Maximum annotation tokens <br/> |2 million <br/> |When an email message is indexed, each word is annotated with different processing instructions that specify how that word should be indexed. Each set of processing instructions is called an annotation token. To maintain the quality of service in Office 365, there is a limit of 2 million annotation tokens for an email message. <br/> |
-|Maximum body size in index <br/> |67 million characters <br/> |The total number of characters in the body of an email message and all its attachments. When an email message is indexed, all text in the body of the message and in all attachments is concatenated into a single string. The maximum size of this string that is indexed is 67 million characters. <br/> |
-|Maximum unique tokens in body <br/> |1 million <br/> |As previously explained, tokens are the result of extracting text from content, removing punctuation and spaces, and then dividing it into words (called tokens) that are stored in the index. For example, the phrase `"cat, mouse, bird, dog, dog"` contains 5 tokens. But only 4 of these are unique tokens. There is a limit of 1 million unique tokens per email message, which helps prevent the index from getting too large with random tokens. <br/> |
+
+<br>
+
+****
+
+|Indexing limit|Maximum value|Description|
+||||
+|Maximum attachment size|150 MB|The maximum size of an email attachment that will parse for indexing. Any attachment that's larger than this limit won't be parsed for indexing, and the message with the attachment will be marked as partially indexed. <p> **Note:** Parsing is the process where the indexing service extracts text from the attachment, removes unnecessary characters like punctuation and spaces, and then divides the text into words (in a process called tokenization), that are then stored in the index.|
+|Maximum number of attachments|250|The maximum number of files attached to an email message that will be parsed for indexing. If a message has more than 250 attachments, the first 250 attachments are parsed and indexed, and the message is marked as partially indexed because it had additional attachments that weren't parsed.|
+|Maximum attachment depth|30|The maximum number of nested attachments that are parsed. For example, if an email message has another message attached to it and the attached message has an attached Word document, the Word document and the attached message will be indexed. This behavior will continue for up to 30 nested attachments.|
+|Maximum number of attached images|0|An image that's attached to an email message is skipped by the parser and isn't indexed.|
+|Maximum time spent parsing an item|30 seconds|A maximum of 30 seconds is spent parsing an item for indexing. If the parsing time exceeds 30 seconds, the item is marked as partially indexed.|
+|Maximum parser output|2 million characters|The maximum amount of text output from the parser that's indexed. For example, if the parser extracted 8 million characters from a document, only the first 2 million characters are indexed.|
+|Maximum annotation tokens|2 million|When an email message is indexed, each word is annotated with different processing instructions that specify how that word should be indexed. Each set of processing instructions is called an annotation token. To maintain the quality of service in Office 365, there is a limit of 2 million annotation tokens for an email message.|
+|Maximum body size in index|67 million characters|The total number of characters in the body of an email message and all its attachments. When an email message is indexed, all text in the body of the message and in all attachments is concatenated into a single string. The maximum size of this string that is indexed is 67 million characters.|
+|Maximum unique tokens in body|1 million|As previously explained, tokens are the result of extracting text from content, removing punctuation and spaces, and then dividing it into words (called tokens) that are stored in the index. For example, the phrase `"cat, mouse, bird, dog, dog"` contains 5 tokens. But only 4 of these are unique tokens. There is a limit of 1 million unique tokens per email message, which helps prevent the index from getting too large with random tokens.|
|||
-
+ ## More information There are additional limits related to different aspects of searching for content, such as content indexing. For more information about these limits, see the following topics:
There are additional limits related to different aspects of searching for conten
- [Search limits for SharePoint Online](/sharepoint/search-limits) For information about content searches, see:
-
+ - [Content search in Microsoft 365](content-search.md) - [Search for content in a Core eDiscovery case](search-for-content-in-core-ediscovery.md)
compliance Prepare Tls 1.2 In Office 365 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/prepare-tls-1.2-in-office-365.md
The [Microsoft TLS 1.0 implementation](https://support.microsoft.com/help/311733
For information about how to remove TLS 1.0 and 1.1 dependencies, see the following white paper: [Solving the TLS 1.0 problem](https://www.microsoft.com/download/details.aspx?id=55266).
+After you upgrade to TLS 1.2, make sure that the cipher suites you're using are supported by Azure Front Door. Microsoft 365 and Azure Front Door have slight differences in cipher suite support. For details, see [What are the current cipher suites supported by Azure Front Door?](/azure/frontdoor/front-door-faq#what-are-the-current-cipher-suites-supported-by-azure-front-door-).
+ ## More information
-We have already begun deprecation of TLS 1.0 and 1.1 as of January 2020. Any clients, devices, or services that connect to Office 365 through TLS 1.0 or 1.1 in our DoD or GCC High instances are unsupported. For our commercial customers of Office 365, deprecation of TLS 1.0 and 1.1 will begin October 15, 2020 and rollout will continue over the following weeks and months.
+We have already begun deprecation of TLS 1.0 and 1.1 as of January 2020. Any clients, devices, or services that connect to Office 365 through TLS 1.0 or 1.1 in our DoD or GCC High instances are unsupported. For our commercial customers of Office 365, deprecation of TLS 1.0 and 1.1 will begin October 15, 2020 and rollout will continue over the following weeks and months.
We recommend that all client-server and browser-server combinations use TLS 1.2 (or a later version) in order to maintain connection to Office 365 services. You might have to update certain client-server and browser-server combinations.
compliance Sensitivity Labels Coauthoring https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-coauthoring.md
This preview version of co-authoring for files encrypted with sensitivity labels
- Users won't be able to apply any labels in Office for the web for Word, Excel, and PowerPoint files that are bigger than 300 MB. For these files, you can use the Office desktop apps to apply a label but you must be the only person who has the file open. -- When you use [DLP policies that use sensitivity labels as conditions](dlp-sensitivity-label-as-condition.md), unencrypted attachments for emails are not supported.
+- Currently rolling out: Support for [DLP policies that use sensitivity labels as conditions](dlp-sensitivity-label-as-condition.md) and unencrypted attachments for emails.
- Some documents are incompatible with sensitivity labels because of features such as [password-protection](https://support.microsoft.com/office/require-a-password-to-open-or-modify-a-workbook-10579f0e-b2d9-4c05-b9f8-4109a6bce643), [shared workbooks](https://support.microsoft.com/office/about-the-shared-workbook-feature-49b833c0-873b-48d8-8bf2-c1c59a628534), or content that includes ActiveX controls. Other reasons are documented in [Troubleshoot co-authoring in Office](https://support.microsoft.com/office/troubleshoot-co-authoring-in-office-bd481512-3f3a-4b6d-b7eb-ebf9d3626ae7). For these documents, you see a message **UPLOAD FAILED** and should select the **Discard Changes** option. Until this issue is addressed, do not label these documents that are identified with this failure message.
compliance Whats New https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/whats-new.md
Whether it be adding new solutions to the [Microsoft 365 compliance center](micr
- [Service encryption with Customer Key](customer-key-overview.md) (Customer Key tenant level DEPs now encrypt sensitivity label configuration for Microsoft Information Protection.)
+### Data connectors
+
+- We have released [17 new data connectors in partnership with 17a-4 LLC](archiving-third-party-data.md#17a-4-data-connectors) and [one new connector in partnership with CellTrust](archiving-third-party-data.md#celltrust-data-connectors). We have also released additional data connectors in partnership with [Veritas](archiving-third-party-data.md#veritas-data-connectors) and [TeleMessage](archiving-third-party-data.md#telemessage-data-connectors). To date, this makes a total of 65 available data connectors to import and archive third-party data to Microsoft 365.
+ ### eDiscovery - [Query and filter content in a review set](review-set-search.md) (new query and filtering capability in a new UX format to filter and search for content in a review set)
enterprise Microsoft 365 Isolation Controls https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/microsoft-365-isolation-controls.md
- Title: "Microsoft 365 isolation controls"-----
-localization_priority: Normal
-- MET150--- Strat_O365_IP-- M365-security-compliance-- NOCSH
-description: Learn how isolation controls work within Microsoft 365, allowing services to inter-operate or remain autonomous as needed.
---
-# Microsoft 365 isolation controls
-
-Microsoft continuously works to ensure that the multi-tenant architecture of Microsoft 365 supports enterprise-level security, confidentiality, privacy, integrity, local, international, and availability [standards](https://www.microsoft.com/TrustCenter/Compliance?service=Office#Icons). The scale and the scope of services provided by Microsoft make it difficult and non-economical to manage Microsoft 365 with significant human interaction. Microsoft 365 services are provided through multiple globally distributed data centers, each highly automated with few operations requiring a human touch or any access to customer content. Our staff supports these services and data centers using automated tools and highly secure remote access.
-
-Microsoft 365 is composed of multiple services that provide important business functionality and contribute to the entire Microsoft 365 experience. Each of these services is self-contained and designed to integrate with one another.
-
-Microsoft 365 is designed with the following principles:
--
-Microsoft 365 services inter-operate with each other, but are designed and implemented so they can be deployed and operated as autonomous services, independent of each other. Microsoft segregates duties and areas of responsibility for Microsoft 365 to reduce opportunities for unauthorized or unintentional modification or misuse of the organization's assets. Microsoft 365 teams have defined roles as part of a comprehensive role-based access control mechanism.
-
-## Customer content isolation
-
-All customer content in a tenant is isolated from other tenants and from operations and systems data used in the management of Microsoft 365. Multiple forms of protection are implemented throughout Microsoft 365 to minimize the risk of compromise of any Microsoft 365 service or application. Multiple forms of protection also prevent unauthorized access to the information of tenants or the Microsoft 365 system itself.
-
-For information about how Microsoft implements logical isolation of tenant data within Microsoft 365, see [Tenant Isolation in Microsoft 365](microsoft-365-tenant-isolation-overview.md).
enterprise Microsoft 365 Isolation In Graph And Delve https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/microsoft-365-isolation-in-graph-and-delve.md
- Title: "Microsoft 365 Tenant Isolation in the Microsoft Graph and Delve"-----
-localization_priority: Normal
-- MET150--- Strat_O365_IP-- M365-security-compliance-- NOCSH
-description: In this article, find an explanation of how Microsoft 365 tenant isolation works in the Office Graph and in Delve.
---
-# Microsoft 365 Tenant Isolation in the Microsoft Graph and Delve
-
-## Tenant Isolation in the Microsoft Graph
-
-The [Microsoft Graph](https://developer.microsoft.com/graph) models activity in Microsoft 365 services, including Exchange Online, SharePoint Online, Yammer, Skype for Business, Azure Active Directory, and more, and in external services, such as other Microsoft services or third-party services. Microsoft Graph components are used throughout Microsoft 365. The Microsoft Graph represents a collection of content and activity, and the relationships between them that happen across the entire Office suite. It uses sophisticated machine learning techniques to connect people to the relevant content, conversations and people around them. For example, the tenant index in SharePoint Online has an Microsoft Graph index that is used to serve Delve queries, the Analytics Processing Engine in SharePoint Online is used to store signals and calculate insights, and Exchange Online calculates each user's recipient cache as input into tenant analytics.
-
-The Microsoft Graph contains information about enterprise objects, such as people and documents, as well as the relationships and interactions among these objects. The relationships and interactions are represented as *edges*. The Microsoft Graph is segmented by tenant such that edges can only exist between *nodes* in the same tenancy. A *node* is an entity with a Uniform Resource Identifier (URI), node type, access control list, and a set of facets containing *metadata* and edges. Each node has associated metadata and edges, arranged into *facets* as in the Common Knowledge Model. *Metadata* are named properties stored on a node which can be used for searching, filtering, or analysis within the Microsoft Graph. A *facet* is a logical collection of metadata and edges on a node. Each facet describes one aspect of a node.
-
-The Microsoft Graph does not bring all the data into a single repository; rather, it stores metadata and relationships about data that lives elsewhere. The Microsoft Graph consists of several data stores and processing components:
--- The Tenant Graph Store provides bulk storage optimized for efficient analytics.-- The Active Content Cache provides quick random access to active node and edges to drive user experiences.-- The input router notifies components internal and external of changes to the tenant graph.-
-Analytics within each workload deduce insights relevant to the tenant-wide calculations and push them to the tenant graph. Tenant analytics reasons over all activity in a tenancy to produce insights into patterns of behavior. For example, Exchange Online calculates the recipient cache for each user with analytics that efficiently reason over each user's mailbox. These per-user analytics produce a set of *RecipientCache Edges* on each person, which are in turn pushed to the tenant graph. This keeps the as much of the analytics processing as close to the source data as possible.
-
-## Tenant Isolation in Delve
-
-As mentioned previously, the Microsoft Graph powers experiences that help people discover and collaborate on current activities in their enterprise, and provides an entity-centric platform for analytics to reason over content and activity across workloads and beyond Microsoft 365. Delve is the first such experience powered by the Microsoft Graph.
-Delve is a Microsoft 365 web experience that surfaces content from Microsoft 365 and Yammer Enterprise to Microsoft 365 users via the Microsoft Graph. The web experience displays data as different boards, each with a certain topic, such as *Trending around me* or *Modified by me*. Each board consists of several document cards that display summary text and a picture from the document. The card lets users do things like open the document or a Yammer page for the document. There is a page for each person in a Microsoft 365 tenant that displays the most relevant documents for this person, and icons that can invoke Exchange Online or Skype for Business for interacting with that person. Because Delve is based on the Microsoft Graph API, it is bound by the tenant-based isolation of that API.
enterprise Microsoft 365 Isolation In Microsoft 365 Search https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/microsoft-365-isolation-in-microsoft-365-search.md
- Title: "Tenant Isolation in Microsoft 365 Search"-----
-localization_priority: Normal
-- MET150--- Strat_O365_IP-- M365-security-compliance-- NOCSH
-description: In this article, find an explanation of how tenant isolation works to separate tenant data in Microsoft 365 Search.
---
-# Tenant Isolation in Microsoft 365 Search
-
-SharePoint Online search uses a tenant separation model that balances the efficiency of shared data structures with protection against information leaking between tenants. With this model, we prevent the Search features from:
--- Returning query results that contain documents from other tenants-- Exposing sufficient information in query results that a skilled user could infer information about other tenants-- Showing schema or settings from another tenant-- Mixing analytics processing information between tenants or store results in the wrong tenant-- Using dictionary entries from another tenant-
-For each type of tenant data, we use one or more layers of protection in the code to prevent accidental leaking of information. The most critical data has the most layers of protection to make sure that a single defect doesn't result in actual or perceived information leakage.
-
-## Tenant Separation for the Search Index
-
-The search index is stored on disk in the servers hosting the index components and the tenants share the index files. A tenant's indexed documents are visible only for queries for that tenant. Three independent mechanisms prevent information leakage:
--- Tenant ID filtering-- Tenant ID term prefixing-- ACL checks-
-All three mechanisms would have to fail for Search to return documents to the wrong tenant.
-
-## Tenant ID Filtering and Tenant ID Term Prefixing
-
-Search prefixes every term that is indexed in the full-text index with the tenant ID. For example, when the term "*foo*" is indexed for a tenant with an ID of "*123*", the entry in the full-text index is "*123foo.*"
-
-Every query is converted to include the tenant ID using a process called tenant ID filtering. For example, the query "*foo*" is converted to "<*guid*>.*foo* AND *tenantID*:<*guid*>", where <*guid*> represents the tenant performing the query. This query conversion occurs within each index node and neither query nor content processing can influence it. Because the tenant ID is added to every query, the frequency of a term in other tenants can't be inferred by looking at best match ranking in one tenant.
-
-Tenant ID term prefixing occurs only in the full-text index. Fielded searches, such as "* Title: foo*", go to a synthetic search index where terms aren't prefixed by tenant ID. Instead, fielded searches are prefixed with the field name. For example, the query "* Title: foo*" is converted to "*fields. Title: foo AND fields.tenantID*:<*guid*>." Because the frequency of a term doesn't influence ranking of hits in the synthetic search index, there's no need for tenant separation by term prefixing. For a fielded search like "* Title: foo*", tenant content separation depends on tenant ID filtering by query conversion.
-
-## Document Access Control List Checks
-
-Search controls access to documents through ACLs that are saved in the search index. Every item is indexed with a set of terms in a special ACL field. The ACL field contains one term per group or user that can view the document. Every query is augmented with a list of access control entry (ACE) terms, one for each group to which the authenticated user belongs.
-
-For example, a query like "<*guid*>.*foo AND tenantID*:<*guid*>" becomes:
-"<*guid*>.*foo AND tenantID*:<*guid*> *AND* (*docACL:*<*ace1*> *OR docACL*:<*ace2*> *OR docACL*:<*ace3*> *...*)"
-
-Because user and group identifiers and hence ACEs are unique, this provides an extra level of security between tenants for documents that are only visible to some users. The same is the case for the special "Everyone except external users" ACE that grants access to regular users in the tenant. But since ACEs for "Everyone" are the same for all tenants, tenant separation for public documents depends on tenant ID filtering. Deny ACEs are also supported. The query augmentation adds a clause that removes a document from the result when there is a match with a deny ACE.
-
-In Exchange Online search, the index is partitioned on mailbox ID for individual user's mailboxes instead of tenant ID (subscription ID) as in SharePoint Online. The partitioning mechanism is the same as SharePoint Online, but there is no ACL filtering.
enterprise Microsoft 365 Tenant Isolation Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/microsoft-365-tenant-isolation-overview.md
- Title: "Tenant Isolation in Microsoft 365"-----
-localization_priority: Normal
-- MET150--- Strat_O365_IP-- M365-security-compliance-- NOCSH
-description: This article contains a summary of how Microsoft enforces tenant isolation in cloud services like Microsoft 365.
---
-# Tenant Isolation in Microsoft 365
-
-One of the primary benefits of cloud computing is concept of a shared, common infrastructure across numerous customers simultaneously, leading to economies of scale. This concept is called *multi-tenancy*. Microsoft works continuously to ensure that the multi-tenant architectures of our cloud services support enterprise-level security, confidentiality, privacy, integrity, and availability standards.
-
-Based upon the significant investments and experience gathered from [Trustworthy Computing](https://www.microsoft.com/trust-center) and the [Security Development Lifecycle](https://www.microsoft.com/securityengineering/sdl/), Microsoft cloud services were designed with the assumption that all tenants are potentially hostile to all other tenants, and we have implemented security measures to prevent the actions of one tenant from affecting the security or service of another tenant, or accessing the content of another tenant.
-
-The two primary goals of maintaining tenant isolation in a multi-tenant environment are:
-
-1. Preventing leakage of, or unauthorized access to, customer content across tenants; and
-2. Preventing the actions of one tenant from adversely affecting the service for another tenant
-
-Multiple forms of protection have been implemented throughout Microsoft 365 to prevent customers from compromising Microsoft 365 services or applications or gaining unauthorized access to the information of other tenants or the Microsoft 365 system itself, including:
--- Logical isolation of customer content within each tenant for Microsoft 365 services is achieved through Azure Active Directory authorization and role-based access control.-- SharePoint Online provides data isolation mechanisms at the storage level.-- Microsoft uses rigorous physical security, background screening, and a multi-layered encryption strategy to protect the confidentiality and integrity of customer content. All Microsoft 365 datacenters have biometric access controls, with most requiring palm prints to gain physical access. In addition, all U.S.-based Microsoft employees are required to successfully complete a standard background check as part of the hiring process. For more information on the controls used for administrative access in Microsoft 365, see [Microsoft 365 Administrative Access Controls](/compliance/assurance/assurance-administrative-access-controls-overview).-- Microsoft 365 uses service-side technologies that encrypt customer content at rest and in transit, including BitLocker, per-file encryption, Transport Layer Security (TLS) and Internet Protocol Security (IPsec). For specific details about encryption in Microsoft 365, see [Data Encryption Technologies in Microsoft 365](../compliance/office-365-encryption-in-the-microsoft-cloud-overview.md).-
-Together, the above-listed protections provide robust logical isolation controls that provide threat protection and mitigation equivalent to that provided by physical isolation alone.
-
-## Related Links
--- [Isolation and Access Control in Azure Active Directory](microsoft-365-isolation-in-azure-active-directory.md)-- [Tenant Isolation in the Office Graph and Delve](microsoft-365-isolation-in-graph-and-delve.md)-- [Tenant Isolation in Microsoft 365 Search](microsoft-365-isolation-in-microsoft-365-search.md)-- [Resource Limits](/compliance/assurance/assurance-resource-limits)-- [Monitoring and Testing Tenant Boundaries](/compliance/assurance/assurance-monitoring-and-testing)-- [Isolation and Access Control in Microsoft 365](microsoft-365-isolation-in-microsoft-365.md)
enterprise Tenant Roadmap Microsoft 365 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/tenant-roadmap-microsoft-365.md
To plan for your tenant implementation:
- [Plan for client app support](microsoft-365-client-support-certificate-based-authentication.md) - [Determine how to use hybrid modern authentication](hybrid-modern-auth-overview.md) - [Plan for Office 2007 and Office 2010 upgrades](plan-upgrade-previous-versions-office.md)-- [Understand tenant isolation](microsoft-365-tenant-isolation-overview.md)
+- [Understand tenant isolation](/compliance/assurance/microsoft-365-isolation-controls)
### Deploy
managed-desktop Test Win11 Mmd https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/managed-desktop/working-with-managed-desktop/test-win11-mmd.md
To date, more than 95% of Microsoft Managed Desktop devices meet [eligibility criteria for Windows 11](/windows/whats-new/windows-11-requirements). You can request details about the eligibility status of your devices from Microsoft Managed Desktop. To file the request, follow these steps:
-1. Open a new service request with the Microsoft Managed Desktop Service Engineering team. If you need more info on how to do file the request, see [Admin support](admin-support.md).
+1. Open a new service request with the Microsoft Managed Desktop Service Engineering team. If you need more info on how to file the request, see [Admin support](admin-support.md).
2. Use these values for the fields: - Title: Windows 11 device eligibility - Request type: Request for information
To enroll your devices in the pre-release test group:
Business-critical applications are the best candidates for more validation in a closed Windows 11 environment. We can help you prioritize apps for Windows 11 testing based on usage and reliability data. To request our recommendations, follow these steps:
-1. Open a new service request with the Microsoft Managed Desktop Service Engineering team. If you need more info on how to do file the request, see [Admin support](admin-support.md).
+1. Open a new service request with the Microsoft Managed Desktop Service Engineering team. If you need more info on how to file the request, see [Admin support](admin-support.md).
2. Use these values for the fields: - Title: Windows 11 Test Base candidates - Request type: Request for information
If you encounter Windows 11 compatibility issues with your line-of-business or M
- Subcategory: Windows Upgrade/Update 3. Describe the behavior and how severely it would hinder your business in a production environment.
-Microsoft Managed Desktop triages and handles issues with pre-release builds based on the effect on productivity. While our service description doesn't cover issues with pre-release builds, we'll confer with customer admins to ensure that issues that block user productivity are resolved prior to starting migration within any given tenant.
+Microsoft Managed Desktop triages and handles issues with pre-release builds based on the effect on productivity. While our service description doesn't cover issues with pre-release builds, we'll confer with customer admins to ensure that issues that block user productivity are resolved prior to starting migration within any given tenant.
test-base Faq https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/test-base/faq.md
Please see the onboarding user guide for more information or contact our team at
**Q: Can Test Base support our automated tests?**
-Yes, Test Base supports automated tests however, we do not support manual tests at this time due to service capabilities.
+**A:** Yes, Test Base supports automated tests, however, we do not support manual tests at this time due to service capabilities.
**Q: What languages and frameworks of automated tests do you support?**
test-base Review https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/test-base/review.md
f1.keywords: NOCSH
- While failed tests, require you to upload a new package.
- You can download the ```test logs``` for further analysis from the ΓÇÿ```Security update results``` and ```Feature updates results``` pages.
+ You can download the ```test logs``` for further analysis from the ```Security update results``` and ```Feature updates results``` pages.
- If you experience repeated test failures, please reach out to testbasepreview@microsoft.com with details of your error.
test-base Uploadapplication https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/test-base/uploadApplication.md
f1.keywords: NOCSH
# Step 2: Uploading a Package
-On the Test Base portal page, navigate to the ΓÇÿUpload new package option on the left navigation bar as shown below:
+On the Test Base portal page, navigate to the **Upload new package** option on the left navigation bar as shown below:
![Upload a new package](Media/Upload-New-Package.png) Once there, follow the steps below to upload a new package.
On the Test details tab, type in your package's name, version and other details
The steps below provides a guide on how to fill out your package details:
-1. **Enter the name to be given your package in the ```ΓÇ£Package name``` field.**
+1. **Enter the name to be given your package in the ```Package name``` field.**
> [!Note] > The package name and version combination entered must be unique within your organization. This is validated by the checkmark as shown below.