More of your employees are working remotely and depending on their mobile device for important company information. The current world climate and the concerns surrounding the COVID-19 virus have only amplified this need.
For many organizations their intranet is the hub for knowledge and information, and the SharePoint mobile app is the best way for employees to access this from any mobile device. A request we have heard from you is to allow the SharePoint mobile app to be more customizable and enable you brand it with your company’s guidelines easily. We are happy to announce that the SharePoint mobile app will now allow admins to customize their tenant theme in the Microsoft 365 admin center. The SharePoint mobile app will allow users to view their tenant theme on the app if admins have configured in on the Microsoft 365 admin center. This ability is available today for both iOS and Android devices.
Company branding with the SharePoint mobile app
For more information on how to customize your tenant them see Customize the Office 365 theme for your organization.
Administrators can configure the following for the SharePoint mobile app:
- Logo Image: Logo of SVG format (Images uploaded in any other format will not display in the app)
- Nav Bar Color: This is background color that appears in the background of the nav bar for all 3 tabs. (Please note sites will not be impacted by this nav bar color input).
- Text and Icon Color: This section input affects text and icons color on the navigation bar
- Accent Color: This input will affect buttons, links and other elements defined on the app for branding.
If you have already configured this information employee will automatically start seeing the branded app after they update the mobile app to latest version.
Customize for your organization
Download or update the SharePoint mobile app from iOS and Android app store today to experience company branding.
![Trainable classifier auto-labeling with sensitivity labels webinar]()
This classification method is particularly well suited to content that isn’t easily identified by either the manual or automated pattern matching methods. This method of classification is more about training a classifier to identify an item based on what the item is, not by elements that are in the item (pattern matching). A classifier learns how to identify a type of content by looking at hundreds of examples of the content you’re interested in classifying
References:
This webinar was presented on Tue Mar 17th 2020, and the recording can be found here.
Attached to this post are:
- The FAQ document that summarizes the questions and answers that came up over the course of both Webinars; and
- A PDF copy of the presentation.
Thanks to those of you who participated during the two sessions and if you haven’t already, don’t forget to check out our resources available on the Tech Community.
Thanks!
@Adam Bell on behalf of the MIP and Compliance CXE team
![Trainable classifier auto-labeling with sensitivity labels webinar]()
Insider risk management is a solution in Microsoft 365 that helps minimize internal risks by enabling you to detect, investigate, and take action on risky activities in your organization.
Communication compliance is part of the new insider risk solution set in Microsoft 365 that helps minimize communication risks by helping you detect, capture, and take remediation actions for inappropriate messages in your organization.
References:
This webinar was presented on Tue Mar 10th 2020, and the recording can be found here.
Attached to this post are:
- The FAQ document that summarizes the questions and answers that came up over the course of both Webinars; and
- A PDF copy of the presentation.
Thanks to those of you who participated during the two sessions and if you haven’t already, don’t forget to check out our resources available on the Tech Community.
Thanks!
@Adam Bell on behalf of the MIP and Compliance CXE team
This week, Vesa and Waldek are joined by Tracy van der Schyff – Microsoft Office 365 Service and Services MVP, learner, keynote speaker, story teller and blogger focused on explaining technology in simple terms, change management and adoption, residing in South Africa.
Did we mention: Tracy is a prolific blogger? Tracy’s idea of March Madness is 31 days of blogging about Power Platform. Then there is her Office 365 learning journey – 365 posts in 365 days. A full index of Tracy’s posts can be found here.
Tracy’s Quotes:
- “If you have to wait until you are an expert to share your learning journey, you would never have anything to say.”
- “People can learn from how you learn.”
- “Force yourself to learn everyday.”
- “Easier to teach a business person a tech skill than to teach a teckie a business process.”
- “Do things right even when doing small things. Because small projects can become large projects.”
- “Products don’t fix problems, people fix problems with products.”
- “Many people need to learn what we have already forgotten.”
- “Try and document”
This episode was recorded on Monday, March 16, 2020
Got feedback, ideas, other input – please do let us know!
![Trainable classifier auto-labeling with sensitivity labels webinar]()
As part of this preview, the Microsoft 365 Compliance Center will allow you to create sensitivity labels and corresponding automatic or recommended labeling policies in Office apps using built-in classifiers.
The six built-in classifiers that are available as part of this preview are:
- Resume: detects written accounts of an applicant’s personal, educational, and professional qualifications and experience
- Source code: detects a set of instructions and statements written in the top 25 computer programming languages of GitHub
- Offensive language: detects text items that contain profanities, slurs, taunts, and disguised expressions (expressions that have the same meaning as more offensive terms)
- Threat: detects a specific category of offensive language related to threat to commit violence or do physical harm/damage to a person/property.
- Harassment: detects a specific category of offensive language related to offensive conduct targeting one or multiple individuals regarding race, color, religion, national origin, gender, sexual orientation, age, disability and genetic information.
- Profanity: detects a specific category of offensive language that contains swear words or vulgar language.
References:
Thanks to those of you who participated in our previews so far. If you haven’t already, don’t forget to check out our preview programs page and our resources available on the Tech Community.
Thanks!
Written by @Nir Hendler , posted by @Adam Bell on behalf of the MIP and Compliance CXE team
![Trainable classifier auto-labeling with sensitivity labels webinar]()
Auto classification for Sensitivity labels in OneDrive for business, SharePoint, and Exchange Online helps you automatically label or tag content as sensitive to ensure the configured protections are applied.
Similar to manual labeling, an administrator can create sensitivity labels and policies to label content based on defined policies or rules. Auto classification varies from manual labeling in that the label occurs within the service, for example SharePoint Online, instead of the user labeling the content.
Additionally, before you publish an auto classification policy – wouldn’t it be great if you knew exactly what files and how many would be affected by your new configuration? This is where the new policy simulation feature will help. Before you enable a policy in your tenant, simulation mode allows you to validate your policy, and tune it further if the results are not quite as expected. The simulation can then be run again to check your update. You can rinse and repeat this process until you’re happy with the results. The ability to safely validate your approach without negatively impacting your environment and end users is critical and should help ease adoption.
References:
Thanks to those of you who participated in our previews so far. If you haven’t already, don’t forget to check out our preview programs page and our resources available on the Tech Community.
Thanks!
Written by @Nir Hendler , posted by @Adam Bell on behalf of the MIP and Compliance CXE team
This week, Vesa and Waldek are joined by Fabian Williams – Microsoft MVP – Visual Studios Development Technologies and Director for the Intelligent Process automation (IPA) practice at Withum located in Washington D.C.
In addition to Microsoft and Community activities and articles, the group focused on this question: Why should a Teams or SharePoint developer care about Azure Functions?
This episode was recorded on Tuesday, March 9, 2020
Got feedback, ideas, other input – please do let us know!
This post is a contribution from Jing Wang, an engineer with the SharePoint Developer Support team.
There are multiple ways to access SharePoint data with custom code, for example, CSOM, JSOM, SharePoint Rest API and Sharepoint Web Service call.
Troubleshooting problems with these accesses likely need correlation IDs of the failed requests. With the correlation IDs we can locate relevant errors in SharePoint ULS logs efficiently.
However, not all failed requests expose the correlation ID to UI, code or through network traces. In those scenarios, being able to set distinctive correlation IDs when send the requests to SharePoint become very useful.
- For CSOM (client object model code), it is straight forward to set it:
ClientContext context = new ClientContext(“https://{site_url}”);
Web web = context.Web;
context.TraceCorrelationId = “88888888111111112222222233333333”;
context.Load(web);
context.ExecuteQuery();
- For JSOM (JavaScript library code):
<script type=”text/javascript”>
var clientContext;
var website;
SP.SOD.registerSod(‘sp.js’, ‘/_layouts/16/sp.js’);
SP.SOD.executeFunc(‘sp.js’, ‘SP.ClientContext’, sharePointReady);
function sharePointReady() {
clientContext = SP.ClientContext.get_current();
website = clientContext.get_web();
clientContext.set_traceCorrelationId(88888888111111112222222233333333′);
clientContext.load(website);
clientContext.executeQueryAsync(onRequestSucceeded, onRequestFailed);
}
function onRequestSucceeded() {alert(website.get_url()); }
function onRequestFailed(sender, args){alert(‘Error: ‘ + args.get_message());}
</script>
- For SharePoint Rest API call：
<input id=”Button” type=”button” value=”Empty Site Recycle Bin” onclick=”runCode()” />
<script type=”text/javascript”>
function runCode(){
SP.SOD.registerSod(‘sp.js’, ‘/_layouts/16/sp.js’);
SP.SOD.executeFunc(‘sp.js’, ‘SP.ClientContext’, emptySiteRecycleBin);
function emptySiteRecycleBin(){
var restUrl = _spPageContextInfo.webAbsoluteUrl+”/_api/site/RecycleBin/deleteAll()”;
$.ajax({
url: restUrl,
type: “POST”,
//withCredentials: true,
headers: {
“X-RequestDigest”: $(“#__REQUESTDIGEST”).val(),
‘SPResponseGuid’: ‘88888888111111112222222233333333‘
},
success: function(response) {alert(“Emptied Site RecycleBin!”);},
error: function(response){ alert(“Error empting RecycleBin…” );}
});
}
}
</script>
Fiddler Trace shows the correlation ID was set successfully:
- For the calls to SharePoint Web Services, for example, listdata.svc or lists.asmx, we can hardcode the correlation IDs as well.
To make a web service call from C# code, you need to create web service reference to the service .svc file first, Visual Studio will generate the reference class for the web service automatically, for example, reference.cs：
The below is the code change needed to add into that class file:
namespace callwebservice.sp2016ws {
using System;
using System.Web.Services;
using System.Diagnostics;
using System.Web.Services.Protocols;
using System.Xml.Serialization;
using System.ComponentModel;
[System.CodeDom.Compiler.GeneratedCodeAttribute(“System.Web.Services”, “4.7.2053.0”)]
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.ComponentModel.DesignerCategoryAttribute(“code”)]
[System.Web.Services.WebServiceBindingAttribute(Name=”ListsSoap”, Namespace=”http://schemas.microsoft.com/sharepoint/soap/“)]
public partial class Lists : System.Web.Services.Protocols.SoapHttpClientProtocol {
private System.Threading.SendOrPostCallback GetListOperationCompleted;
…
protected override System.Net.WebRequest GetWebRequest(Uri uri)
{
var request = base.GetWebRequest(uri);
request.Headers.Add(“SPResponseGuid”,”88888888111111112222222233333333“);
return request;
}
In this episode, Vesa and Waldek are joined by Franck Cornu – Office 365 developer, architect and owner of aequos out of Montreal, Canada. Franck’s strength is bringing and bridging 3 perspectives – Developer, Architect and Functional Consultant, in every customer conversation. His collaborative approach is – define the backlog together, translate to functional requirements, consider functionality available from community and then define requirements for code, test and final delivery. Lately, Franck has been very actively contributing to the PnP Modern SharePoint Search solution web part.
This episode was recorded on Tuesday, March 3, 2020
Got feedback, ideas, other input – please do let us know!
In this episode, Vesa and Waldek are joined by Karoliina Kettukari – MVP and Microsoft Teams and Office 365 user adoption and change management consultant with Sulava in Helsinki, Finland. Their conversation focuses on the human side of technology deployments, not addressed by the mere roll-out/announcement of a new technology. It is clear, change is constant and change impacts people throughout the entire organization – directly and more often indirectly.
This episode was recorded on Monday, February 24, 2020
