Troubleshooting & FAQ
Quick Diagnostic Checklist
When an export or sync fails, or results don't appear as expected, work through these steps in order:
- Confirm the integration method. Is the automated sync or the IMDF export being used? To connect to pre-existing Exchange resources, the IMDF export must be used.
- If using the IMDF export, verify name alignment. Cross-reference all location names in Mappedin Maker with the resource display names in Microsoft Places or the exported CSV. Names must match exactly (case-sensitive & spelling).
- Check for duplicate locations. Open the Locations panel in Maker and look for duplicate location names or a single location attached to multiple spaces.
- Check room doors. If rooms are missing from Places, verify every room has at least one door. Rooms without doors are exported as "nonpublic" and hidden.
- Check desk orientation. If desks appear rotated incorrectly, verify the rotation stem direction.
Frequently Asked Questions
Export and Sync
My export or sync keeps failing. What should I check first?
The most common cause is location name duplication. For the IMDF export, verify that the CSV resource names and Mappedin location names match.
Should I use the automated sync or the IMDF export?
The two methods serve different environments. The IMDF export supports pre-existing Exchange resources and provides full control over the IMDF output via PowerShell. The automated sync handles resource creation and IMDF upload in a single step from Mappedin Maker. See the method comparison for details.
Can the automated sync be used with pre-existing Exchange resources?
No. The automated sync creates its own resources and cannot connect to pre-existing ones. To link to existing rooms or desks in Exchange, use the IMDF export.
The sync was partially successful. What happened?
Each resource creation during a sync is an independent operation. If some succeed and others fail, the successful ones already exist in Places. Review which resources were created, fix the issues that caused failures, and retry. The sync does not roll back previously created resources.
Rooms
Rooms are not showing up in Places.
Check that every room has at least one door. Rooms without an entrance are automatically categorized as "nonpublic" in the IMDF file and hidden in Places. Also verify the room has a location label and the name matches what is configured in Places.
Why don't kitchen icons show up in Places?
Places currently renders icons for restrooms, stairs/escalators, and elevators. Kitchen icons are not displayed.
Desks
Desks look rotated incorrectly in Places.
In Maker, select each desk object and check that the rotation stem is pointing upward. If the issue persists, enable the Preserve Rotation toggle in the export's advanced options.
Desks are difficult to see in Places.
Desks currently require significant zoom to become visible in Microsoft Places.
Configuration
What Microsoft subscription is required?
See Microsoft's license requirements.
Is an Exchange Online mailbox required?
Yes. Places requires Exchange Online. On-premises mailboxes are not supported.
Can a multi-building campus map be sent to Places?
No. The Places integration supports a single building at a time. Multiple buildings must each be mapped as a separate venue in Maker and synced or exported individually.
Can the same building be synced to multiple tenants?
Yes. Synced resources are tracked per tenant ID.
Is a live map required?
No. Both draft and live maps can be synced or exported.
How long before changes show up?
Usually within a few hours, but new or updated resources can take up to 48 hours to appear in Microsoft 365 apps.
Why do some walls not appear in Places?
Places only renders fully enclosed walls. Partial walls or room dividers that do not form a complete enclosure will not appear on the map.
Known Limitations
The following are known limitations in the current Microsoft Places integration:
| Limitation | Details |
|---|---|
| Kitchen icons not displayed | Kitchen icons are not currently rendered in Places. |
| Desk visibility at low zoom | Desk icons require significant zoom to become visible in the Places UI. |
| Propagation delays | New or updated resources can take up to 48 hours to appear in Microsoft 365 apps. |