This is a reminder for myself, sometimes I need to access to the admin portal of each product, but I’m not able to remember all those URL’s, so with this post I’ll try to keep this url’s on my mind.
Hopet it helps!
While I was trying to connect to the S4B Online admin center by PowerShell I received the following error: “Unable to discover PowerShell endpoing URI”
I used the following PowerShell commands to connect to the admincenter:
So, as you can see the only method allowed to connect to the S4B admin center is by explicity using the domain:
$cssession = New-CsOnlineSession –Credential $credential –OverrideAdminDomain “domainname.onmicrosoft.com”
It is very straightforward to solve the error, but I hope that it will help someone
We are living in a digital transformation to O365, but by the time we are doing this, our customers still need to connect their On-Premises data like SharePoint or SQL to Office 365 applications (PowerApps, Microsoft Flow, Logic Apps, Power BI).
For that reason, Microsoft has introduced on-premises data gateway for providing a quick and secure connection between on premise data and Office 365 apps.
We must keep in mind that there are two different types of gateways, one of them is On-Premises and the other gateway, is the personal gateway, which only allows to connect to PowerBI and can be used as an individual without any administrator configuration.
In the following image, we can see the differences between the personal gateway and the On-Premises gateway:
Moreover, the current supported On-Premises applications are SharePoint 2016 and SQL 2016, as you can see in the diagram below, there are multiple O365 connections to On-Premises services:
The installation process is straightforward, and only is needed a server with the following requirement to use the gateway:
||Version – 4.5
||Windows 7 / Windows Server 2008 R2, or later
If you require more info about the gateway, you can follow the links:
Many clients are adopting Microsoft Teams as the central tool for productivity and collaboration, it is great to see an application that unifies functionalities like video, call and the collaboration tools from SharePoint as well as the integration with other applications or even third party applications.
But, what happens when the Microsoft Teams application fails? Where we can troubleshoot what is happening?
It is true that we can navigate to the Tech Community to try to research for some information, but its not the best, so how we can obtain more information?
By using the magic key combination: Ctrl – Shift – Alt – 1
We will be able to download a log file:
Where we will see pieces of JSON formatted text and the most interesting part, lines that have time stamp and message level and of course, an error message.
Also, we have the leves categorized as:
- War : Warning
- Err: Error
- Inf: Information
So, doing this we will be able to troubleshoot Microsoft Teams, and at least obtain a clue of what the hell is happening with the app.
Hope that helps!
Recently I’d been involved in a O365 project where the client need to use Skype for Business Online, but they have the mail in other platform which is not Exchange Online (I hope they will migrate in a near future). So, the question is: How can they schedule meetings for Skype for Business?
As well as MS has a solution to Schedule meetings in OnPremises, for Skype Online we have a similar solution, which is “Skype for Business Web Scheduler”, very original, isn’t it?
This solution is a web-based program that you can use to create Skype Meetings, in case you don’t have Outlook. The only thing you need is an Internet connection (we are in O365, bravo captain obvius!)
So, we’ll need to navigate to https://sched.lync.com sign in with your work account, and the scheduler will be presented. For people that has been using Skype Scheduler with Outlook, will be very similar to it.
If you have any doubts or need support about this tool, check the following link
Hope that helps!
Recently, due to client requirements we’re doing a series of tests about how to migrate a bunch of attributes to O365. But we found a simple (and silly) problem that stuck us for a couple of hours.
At first glance, we were able to migrate some users from OnPrem to Office 365, but then we started playing with some other AD attributes, one of them, was ProxyAddress.
We were trying to set the following proxyaddress onprem and try to synchronize it in O365: email@example.com. At first glance, everything seems ok, because we were able to see in the ADConnect client that this attribute was exported to O365, but when we tried to examine this attribute in O365, was impossible to sync it.
We did a lot of things, and we run a lot of tests, including full syncs, delta, etc… and finally we discovered that it is not possible to sync a proxyaddress from onprem to o365, which contains *.onmicrosoft.com.
So, sometimes we have to follow KISS procedure and try to no rebuild the wheel…
Hope that helps!
When I start a project with a customer, they ask me to asses them in order to evaluate which ports and IP’s are necessary to be opened in order to work with Office 365 services.
Whenever I can, I try to give them a complete solution, but in other cases I heard from them how complicated is to configure the firewalls due to the number of IP ranges and ports required for Office 365.
How customers are not sure which services will be used I give them the following URL: IP’s and Ports
So, by using the following link, will be very easy for them to configure the services and to use them in a proper way.
till next time!