A lot has changed in Yammer over the past year and we continue to see new growth, new communities, and new users getting started with Yammer. With this in mind, we are excited to share training videos that you can use to share within your own organization.
Use these training videos to build momentum in your Yammer communities.
A long-requested feature to send emails from an alias in Office 365 seems to be finally released. The feature has not been announced yet, but it’s already documented in the service description and seems to work fine. This new feature should become available for Outlook ... Read moreHow-to Send email from Alias in Microsoft Office 365
April 20th, 2021 by Jared Spataro, Corporate Vice President for Microsoft 365
One thing is certain: hybrid work is the future of work. People want increased flexibility and a blended work model that grants them the freedom to work when and where it’s most comfortable for them. Hybrid work can deliver a future that people want and a future that I think will be better—but that doesn’t…
I decided to take this challenge on as a way to bolster my Azure skills. Working with a project is the best way to build skills. You often run into problems or challenges that require diving deeper into the technology, thereby building knowledge.
I’m not sure how many parts this series will end up being, but here in part 1 I will cover:
Storing the project in GitHub
Building the website
Creating the Azure resources
Deploying the website
I won’t be going into step-by-step detail of how I built everything, but I will link to resources that I used along the way.
Storing the Project in GitHub
At the end of this project, I want to deploy website updates automatically out to Azure. With this in mind, I created a repository out in GitHub to store the project artifacts. I cloned the empty repository to my laptop. You can view the repository here:
Following Gwen’s advice in the announcement post, I copied this free resume template to a folder named website in my project repo. I began customizing the text to put some information about myself, certifications, and previous experience.
There is a new Azure service call Azure Static Web Apps that automatically builds and deploys full stack web apps from a code repository. While this service is purpose built for this project, Azure Static Web Apps is still in public preview at the time of this writing. That will be another project for the future.
Using the Azure CLI, I created a resource group and storage account. In the storage account, I enabled the static website hosting and uploaded the website content to the storage account. Finally, I retrieved the default website URL to verify the site loads.
I wrote a PowerShell script to deploy the resources. The script is basic and doesn’t have any error handling, but it deploys all the resources that I need so far. You can view the script in the project repo:
As part of the build script, I uploaded the website files from my local system to the $web container in the storage account. The script ends with displaying the default URL for the website in the storage account. You can view my site so far here.
If you don’t use the above script to display the website URL, navigate to your storage account to Settings > Static website. Here you enable or disable the static website using the blob service, retrieve the primary endpoint URL, and configure the index and error document names.
I need to enable HTTPs and custom domain support. Given I already have a domain, I may just put a CNAME record to point to the default website URL. It probably depends on how much a new domain is going to cost. I also need to implement the visitor counter using an Azure Function and Cosmos DB.
If you are using Exchange Server 2019, running on Windows Server 2019 and Office Online Server (Office Web Apps) running on Windows Server 2016 or older operating systems, you will get an error as shown below: “Sorry, there was a problem and we can’t open this document. If this happens again, try opening the document […]
Today I want to explain to you, my loyal blog followers, why you need to set up Navigation Audience Targeting when you share content externally in SharePoint. As an example, I will use a very typical use case to explain what the issue is all about and then explain how to avoid it.
You have a Team site connected to a company/Intranet Hub or some other Hub you have in your environment
When the recipient (external user) access the shared files and folders on a given SharePoint site, the recipient gets access to just the shared files and folders, BUT ALSO gets to see the Hub navigation that propagates to all the associated sites.
In the below example, I shared a folder with an external user, and the external recipient also gets to see your Hub Navigation as well! Now, everything in SharePoint is security-driven; however, hub navigation is not (by default). So while the recipient won’t be able to access any of those links, you might still not want the external users to see the names of the sites you have either.
How to enable the Hub Navigation Audience Targeting
To mitigate the issue described above, you would need to set up Navigation Audience Targeting on your Hub Navigation. To make it happen, please reference this post for the step by step instructions.
To hide ALL the links from the external recipients, you would need to set Audience Targeting on ALL the links you have in the navigation