Veeam Backup for Microsoft Office 365 Self-Service Web Portal v5 release with Teams support!

Veeam Backup for Microsoft Office 365 Self-Service Web Portal v5 release with Teams support!

Veeam released v5 of Veeam Backup for Microsoft Office 365 last year which added the highly anticipated Teams support. Since the release, I’ve had requests for Teams support within the Unofficial Self-Service Web Portal. While I was already working on it during the beta, it is not a small feature to add. On top of that, I wanted to resolve some bugs and missing features combining them with under the hood enhancements.

Today, I’m happy to announce support for Teams within the portal supporting restores or exports for Posts, Files and Tabs.

I’ve provided a full list of all changes at the end of this post but let’s have a closer look at some of the new features.

Teams support

Teams support has been added as a new standalone page.

It has been designed in the following way.

All the Teams are listed on the left panel. In the middle part, we’ll see all the available channels and on the right, we’ll see the relevant content being it Files, Posts or Tabs.

When it comes to files, you will be able to download and restore those back to the original location. Posts can be exported or all of them can be restored at once to the original location. Tabs can be restored to the original location.

You’ll notice that all conversations are clickable as well. This will show a popup with the details of that specific conversation as well as restore options.

New UI enhancements

Some other new enhancements across all “Explorer” views is the fact that you can now do mass restores more easily for select items or a full folder or account. The below is an example of an Inbox folder in Exchange.

On the main index page, there are a few changes such as improved menu items and a new “Sessions” panel to the dashboard page. The panels are now also on a maximum fixed width to support those widescreen monitors.

How to upgrade?

Important: due to a new limit parameter in the config file, it is advised to do a new installation. If you use the old config file, it will work but a default limit (250) will be used. This means that for all API requests, a maximum of 250 items will be requested. By using the config file, you can decrease or increase it.

In order to upgrade, perform the following steps:

  • Take a backup of config.php so you don’t forget your custom settings
  • Head on over to GitHub
  • Follow the installation instructions again to overwrite all files – due to major changes it really is recommended!
  • Either run setup.php again or adjust the config.php file based upon the original config.php files – make sure to change the host, port (if required) and title

What’s new?

New features:

  • Added Teams support
  • Added default items limit of 250 in the configuration file
    • This can be adjusted to any value to load more items at once
    • If there is no number defined in the configuration file, the default will be 250 (advised for VBO v4)

UI enhancements:

  • General
    • Added a note on how to get the application ID accross the whole portal
    • Dashboard panels are now limited in maximum width
    • Resolved logout issue resulting in a stuck browser session
    • Unified the wizard popup titles to clarify what is happening
    • The left side menu will now correctly show which Exchange/OneDrive account is selected
    • Updated colors for clarification of the selected item in the left side menu
  • History overview
    • Renamed “Activity” to “History”
    • Added “History” to the dashboard
    • The history session log popup now shows the session date and timestamp
  • Jobs overview
    • Added description field
    • Resolved issue with enable/disable buttons always being set to Disable by default on the Jobs overview
  • Repository overview
    • Removed duplicate “Capacity Limit” from Repositories View
  • Restore
    • Implemented new “Restore” and “Export” buttons for restoring “All” or “Multiple selected” items for Exchange/OneDrive/SharePoint
    • Renamed “Options” button to “Restore” for clarification
    • Starting a restore session will hide other services from the top menu
    • Resolved issue with expired restore sessions resulting in a stuck browser session
    • Resolved Exchange export issue when trying to export an item with a subject that contains special characters such as ‘ ” ( )

10 thoughts on “Veeam Backup for Microsoft Office 365 Self-Service Web Portal v5 release with Teams support!

  1. I really love this portal, great work.
    One question though, after upgrading to v5 I get this error when logging in with the organization admin credentials:
    Error: Resource is not available with Organization authentication.

    No issues with that in v4.

    1. Hi Berend, I was made aware of the issue over the weekend. I have just published a fix to this (and one more issue). Can u try the updated code and see if the issue is resolved?

    1. Can u verify it is 100% the latest files you are using? As the fix worked for several others. Are you using MFA or basic authentication as a tenant?

  2. Hello Niels,
    I completely remove my wwwroot content, download the new version, copy all files to wwwroot, modify config.php, remove setup.php, restart IIS.
    Then I get:
    Deze pagina werkt momenteel nietlocalhost kan dit verzoek momenteel niet verwerken.
    HTTP ERROR 500

    1. This looks like an issue with web config as it states error 500 which is an internal server error. IIS error logs will give you more clarification (could be permission issue or something). Did u download or git clone those files?

      1. I checked the Github again and saw some files were changed yesterday. I downloaded and replaced my files and now everything works fine.
        Thanks again.

  3. hi. Great work!
    Two things:
    – why isn’t there an official release on github of v5?
    – it would be nice if you deliver a VERSION file containing the current version of the release to be able to do release checks on installed version vs latest git release version

    1. Hi,

      On the version on GitHub, this is on my todo for the upcoming week. I’ve learned from previous releases that it’s better to hold off on this for 1-1.5 months in case of (major) bug fixes and issues.

      For a version file, that’s a good suggestion and I’ll look into it.

      Thanks.

Comments are closed.

Comments are closed.