Building Data import interface and method needs MAJOR overhaul. The method available currently, of populating a CSV or TSV file with 14 mandatory fields (blanks are ok, but still need the column) is absolutely unwieldy and burdensome to put it mildly. For some companies with a limited set of subnets and locations, it seems fine. But large, global corporations with locations if many dozens of countries, and dozens of offices within any country, this import method is obsolete. Microsoft needs to build a tool or script that can import from a variety of common source formats, or even pull from on-prem AD, in such as way to create the file so that it can be imported without constant problems or errors. This file method is also prone to errors for seemingly no reason. One minute it imports data fine. You take the exact same file, update some data, and the file now fails. Sometimes this was only minutes apart! I exported data from our AD Sites and Services, re-arranged the subnets to fit in to the file as a starting point, but the upload tool has no method to assist in clearing overlapping IP subnets or pre-checking the entire file for problems. It only tells you one error at a time. Then you need to correct, re-import and do it all again. I have over 1000 lines and already I super-netted or resolved subnet overlapping manually. It's still complaining! Really very bad as it is now - this needs work if you expect companies to really use the data.
Anon E Mousse commented
Yes, this is a Teams related request. And it's still a big problem. Microsoft doesn't make it easy at all to enter building/site data in to Teams. Maybe it's fine for very small networks, few office locations. But if you are managing Teams in a large environment with many office locations, different capabilities for each building, etc the existing method doesn't work at all.
Anthony G commented
is this for MS teams? not sure it is, but your in the MS teams forum,...