Join for quick access. Enter your email below and we'll send confirmation plus sign you up to our newsletter.
By submitting your information, you confirm you are aged 16 or over,
have read our
Privacy Policy
and agree to the
Terms & Conditions. Geographical rules apply.
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
You are now subscribed
Your newsletter sign-up was successful
Join the club
Get full access to premium articles, exclusive features and a growing list of member rewards.
An account already exists for this email address, please log in.
Microsoft Online Services are built on a Windows Server 2003 foundation. An SPS infrastructure doesn’t need the latest bells and whistles. It really needs time-hardened management and centralized security features. Not much has changed in the way of securing the connection from clients to back-end servers. What was bulletproof five years ago remains so today. Similarly, there’s no need to reinvent the wheel and use Microsoft Online Services to test run new platforms. The Microsoft Solution for Hosted Messaging and Collaboration that powers part of BPOS was already in its 3.0 revision way back in January 2005. Years ago, people used to joke that it took Microsoft three tries to get something right. Even if true, the server platforms underneath BPOS are well beyond that point.
For years, Microsoft has known that its future depended on security. Perhaps you remember in the lead-up to Windows XP’s launch that Bill Gates and others at Microsoft discussed many steps having been implemented to change how software was developed and tested for security within the company. One outcome of this was the Microsoft Trustworthy Computing Security Development Cycle, better known as SDL. If you want the full run-down on SDL, check out this link. Otherwise, just know that SDL assesses possible threats to software as that software is being designed, tests whether or not holes are being remedied, and mandates a thorough code review and security assessment before launch. Every element of Microsoft Online Services went through this process.
Naturally, Microsoft uses a range of hardware firewall and IP filtering appliances at each edge interface with the public Internet. Servers at these boundaries run Microsoft Forefront Security, the company’s enterprise-level anti-malware platform. With this, even if you inadvertently try to upload an infected file to a SharePoint site, for example, the file will be scanned, flagged, and quarantined before it ever reaches actual data servers. Just as information is protected within the data center, it’s also protected in transit. End-user browser sessions are safeguarded by strong encryption, and the connections running between Microsoft data centers are all run through VPNs.
So basically it's good for the mid-size/emerging businesses? I think it's a move in the right direction, although in the current times I would like to see Microsoft focus a bit more on Small Business Solutions rather than for bigger companies, only because for the Small Businesses it's a lot harder to spend even 1000$ on something.
William said: For example, in Exchange Online, there’s no more PowerShell, scripting, or similar nuances for tweaking.
I understand the article is almost 2 years old, but that is a plain wrong statement. You can ceratinly use PowerShell or Migration Tool Command Shell with Exchange Online. You should update the article sir.
William said: For example, in Exchange Online, there’s no more PowerShell, scripting, or similar nuances for tweaking.
I understand the article is almost 2 years old, but that is a plain wrong statement. You can ceratinly use PowerShell or Migration Tool Command Shell with Exchange Online. You should update the article sir.
