No, it's not "best practice". Implementing SSL interception is a trade off, every companies that are considering it have to weigh the downsides of SSL interception heavily.
On one side, implementing SSL interception centralises management of security. It allows the company to scan for malware, and to detect and block (accidental) data exfiltration/leaks, it also allows the company to enforce policies like prohibiting access to NSFW sites.
On the other side, it also makes the job of the attacker much easier as they now have a single high value machine that can compromise the security of the entire company. Compromising this single machine would allow the attacker to intercept every passwords, spoof pages, and distribute malware at unprecedented level.
Additionally, many SSL interception products actually have poorer security than up-to-date browsers, for example, not checking certificate chain correctly, not checking OCSP/CRL, or their root certificate store may not be updated as frequently as browser root store. Most of the interception products in the market is a net negative to security when they aren't implemented properly. Getting net positive from the better interception products are not easy, you cannot just install and forget, they need continuous maintenance, if they have data exfiltration detection, their signature database need to be kept up to date as the business evolves. Implenting interception properly requires a significant investment for somewhat modest benefits.
Common but poor reasons for implementing SSL interception is that SSL interception couldn't really detect or block deliberate data exfiltration. If you don't trust your employees, you have social problem, not technical, and you can't fix social problem with technical solutions.
Another common and poor reason is that it allows the administrators to not have to setup antivirus on individual workstations. Many viruses cannot be detected with static analysis, administrators that uses central antivirus to replace, rather than in addition, to per-workstation antivirus should have their administrator privilege revoked.
Having implemented SSL interception also should never be used as an excuse to keep outdated software that cannot support modern TLS (e.g. IE6 on WinXP).
There are cases where implementing interception makes sense, but most vendors if these products overstates what their product can actually do, and significantly downplays the costs and downsides. Most offices wouldn't really benefit from SSL interception, and usually increase their risks by implementing it.