This post has been republished via RSS; it originally appeared at: SharePoint Support Blog articles.
In both scenarios discussed above, the documents/items are searchable when searching using the managed property explicitly. For Example: listitemid:6
Older farms were configured so that farm schema (this is different from the tenant schema and is managed by Microsoft) had the ID included in the fulltext index. This resulted in the ability of users to be do freeform search for an item/document id. In this instance it would include the item/document in most cases even though the managed property for listitemid is not configured to have this as part of the fulltext index at the tenant level.
This configuration, that was present on older farms has been modified for performance improvements and based on feedback from customer that this behavior caused unexpected results. As a result, farm schema no longer adds the ID to the fulltext index so the you will need to explicitly search using the managed property listitemid:<ID>. As tenants are moved from one farm to another farm as part of planned capacity operations, you will experience scenario 1 that was outlined above. For scenario 2 that was outlined above, this is due to one tenant being on an older farm and the other being on a newer farm.
Note: We recommend making the Managed Properties that you are going to use on more than one site at the Tenant level as a best practice.
2. Go to search
3. Go to Manage search schema
4. Click on “Create a new managed property”
5. Give it a name and make sure that the following options are checked: Searchable, Queryable, Retrievable, Token Normalization