ProcMon 3.80, Sysmon 13.20, TCPView 4.10, ProcExp 16.40, PsExec 2.34, Sigcheck 2.81 and WinObj 3.10
This article is contributed. See the original author and article here.
This article is contributed. See the original author and article here.
This article is contributed. See the original author and article here.
SharePoint Syntex brings advanced AI-powered content management to SharePoint & Microsoft 365. We’re continuing to work with our customers and partners to make updates and improvements. Here are the latest updates to support powerful AI models that transform content into knowledge.

Coming soon, you can automatically set sensitivity labels in document understanding models. This is in addition to the ability to automatically apply retention labels. Applying sensitivity labels (aka Microsoft Information Protection or “MIP” labels) enables you to classify and protect your organization’s data, while making sure that productivity isn’t hindered.
Automatic sensitivity labels are important because:
These changes will start to rollout to Targeted Release users in May 2021, and can be tracked on the Microsoft 365 Public Roadmap ID 81975.
This month we also added a new regular expression (RegEx) explanation type, allowing you to provide more complex explanations when training a model. This update includes a set of RegEx explanation templates that can be used or edited like other explanation templates, such as date, currency, and phone number.
Regular expressions provide a powerful, flexible, and efficient method for processing text. The extensive pattern-matching notation of regular expressions enables you to quickly parse large amounts of text to find specific character patterns.
This update will also start rollout to Targeted Release users in May 2021, and can be tracked on the Microsoft 365 Public Roadmap ID 81976.
We’re thrilled to announce the release of or Syntex developer community n GitHub. Visit our GitHub repository for Syntex community work to get community samples that demonstrate different usage patterns of Document Understanding models in Syntex. To start you off, we included four samples focused on benefit changes, contract notices, services agreements, and trade confirmations.
The samples in this repository contain both the Document Understanding model files, as well as the files used to train the model. Once imported in your Syntex Content Center site, you’ll be able to use these models to process files, as well as view and edit the key model elements – the classifier and extractors – to match your needs. If you want to further deploy the model, then checkout the Deploying Models article to learn more.
You can also use this repository to submit a community contribution, view the issue list, and participate in a discussion forum.
We’re continuing to improve and enhance SharePoint Syntex and we’ll share new features with you as they become available. To stay up to date on Knowledge and Content Services, and products updates like those listed here, subscribe to the Microsoft Viva newsletter.
This article is contributed. See the original author and article here.
Microsoft Viva Connections brings the next generation, personalized, Intranet to where people work… namely within Microsoft Teams. In this HLS Show Me How post Microsoft’s Scott Moore and Michael Gannotti walk you through all the elements of setting up and deploying Microsoft Viva Connections.
Covered in these videos:
Set up an organizational Home Site in SharePoint Online
Create the Microsoft Viva Connections Package
Upload the Microsoft Viva Connections Package to Microsoft Teams
Setup the Viva Connections App in Microsoft Teams Admin Center under App setup policies/Global
Resources:
Thanks for visiting – Michael Gannotti LinkedIn | Twitter
Michael Gannotti
This article is contributed. See the original author and article here.
Every day in Azure, we spend time working with customers who are bringing mission critical enterprise workloads to Kubernetes with AKS. Their requirements drive our roadmap, ensuring that we are balancing the innovative capabilities of the cloud native ecosystem with the requirements of some of the world’s largest companies.
Many AKS customers are subject to the compliance requirements of a specific industry, such as finance, healthcare, or government services. Meeting those requirements can be onerous at the best of times, but it can be even more difficult to do in the context of Kubernetes, where patterns are nascent and flexibility is limited. To help address this challenge, we are announcing AKS for regulated industries, a collection of guidance, benchmarks, and best practices that makes it simpler for customers subject to those constraints to be successful on AKS. This includes a baseline cluster architecture for regulated industries, specific guidance for customers seeking Payment Card Industry (PCI) compliance, and an AKS-specific security benchmark published by the Center of Internet Security (CIS).
In support of that initiative, we are also pleased to announce a series of new product capabilities that will help customers deliver mission critical workloads with Kubernetes on Azure. First, we are excited to become the first cloud provider to offer integrated Kubernetes agent nodes meeting the Federal Information Processing Standards (FIPS) compliance bar, now available in public preview. With a single CLI flag and at no extra charge, AKS customers can now obtain a version of Ubuntu 18.04 that includes the necessary components for their agent nodes to be FIPS compliant. Windows Server-based agent nodes will follow in just a couple of weeks. Speaking of agent nodes, we are also announcing today the general availability of host-based encryption for AKS agent nodes. This capability provides an additional layer of security as OS, temp, and data disks can now be automatically encrypted with either platform or customer-managed keys. Finally, we are pleased to announce the general availability of Azure role-based access control (RBAC) for Kubernetes. This capability allows customers to manage granular access to AKS and Arc-connected Kubernetes clusters at scale leveraging the same framework that they use for all other Azure resources.
Of course, when it comes to meeting the needs of the enterprise, security is just one piece of the picture. Today, we are excited to announce several other capabilities designed meet the needs of our largest customers. We recently announced previews for cluster auto-upgrade, the ability to have AKS automatically trigger upgrade of your clusters, and planned maintenance, the ability to signal to the service when you would prefer to have potential impactful maintenance operations occur. Now, you can combine those two features with the integration of auto-upgrade with planned maintenance, ensuring that any potential disruptions from a cluster upgrade occur at a time that minimizes business impact.
Finally, we know how important it is for customers to stay up-to-date with the latest innovation happening in the Kubernetes community. That’s why we’re proud to once again lead the way among cloud providers in offering the latest upstream releases in AKS, with the preview of Kubernetes 1.21. This release includes a number of significant improvements, including the graduation of CronJobs and immutable secrets/configmaps to stable. Please give it a try and let us know if you have any trouble by logging an issue on GitHub.
This year’s //build conference marks an exciting milestone in the Kubernetes on Azure journey. No longer are customers simply looking for the core capabilities required to make their initial applications run in a cloud native environment. Now they are looking for the guidance and advanced features required to meet the high bar set by their most crucial workloads. Azure is committed to meeting those needs by building a platform that is enterprise-grade, by design. And with the announcement of application services for Kubernetes clusters, we are making it easier than ever for developers to build on top of the platform.
This article is contributed. See the original author and article here.
Today, businesses require big data streaming platforms and event ingestion services that can process millions of events per second to build dynamic data pipelines and immediately respond to business challenges. Azure Event Hubs, a fully managed, real-time data ingestion service, is designed to serve demanding big data streaming and event ingestion needs.
Today, we are announcing the public preview of Azure Event Hubs Premium, a new product SKU that is tailor-made for high-end event streaming scenarios which require elastic, superior performance with predictable latency.
Azure Event Hubs premium comes with reserved compute, memory, and storage resources, which increases the performance and minimize cross-tenant interference in a managed multi-tenant PaaS environment. Event Hubs premium introduces a brand-new log storage engine that drastically improves the data ingress performance and substantially reduce the end-to-end latency. On top of all the capabilities and protocol support of the Event Hubs Standard offering, Event Hubs Premium offers, and far more generous quota allocations.
Here are some of the key compelling benefits of Event Hubs Premium SKU.
Event Hubs premium uses a new, two-tier, native-code log engine that provides far more predictable and much lower send and end-to-end latencies than the prior generation, without any durability compromises. This enables you to ingest and processes large volumes of events and data with high throughput, low latency, and high reliability (events are triple replicated across Azure availability zones).
With Event Hubs premium you get reserved compute, memory, and storage resources for each tenant to achieve more predictable latency and far reduced cross-tenant interference risk in a multi-tenant PaaS environment.
As Event Hubs Premium is a multitenant offering, it can dynamically scale more flexibly and very quickly. Capacity of Event Hubs Premium tier is allocated in Processing Units which correspond to a share of isolated resources (CPU, Memory, and Storage) in the underlying infrastructure. Therefore, there are no throttling limits are applied for your data ingestion scenarios and you stream events up to the maximum level that the allocated processing units can handle (which can depend on multiple factors such as number of producers and consumers, payload size, partition count, and many more).
Events Hubs premium can bring you cost savings for certain use cases where you don’t need the power of a single tenant dedicated Event Hubs cluster, but you need to handle data streaming workloads that are beyond the limits of the standard tier.
Event Hubs Premium SKU is suitable for streaming use cases that require more throughput, isolation, and predictability than Standard SKU, while you don’t need a dedicated single tenant cluster which is intended for most demanding streaming needs at a higher price point.
If your data streaming use case needs very high number of throughput units of the standard SKU, then EventHub premium may offer better performance, minimal cross-tenant interference, more generous quota allocations and additional features for the same cost.
If the use case does not need the power of a dedicated single tenant cluster, compared to the Dedicated SKU, Event Hubs Premium can provide benefits such as dynamic scaling and the same reliability support (premium namespaces support AZs without the need to allocate extra capacity.)
To try out and learn more about Azure Event Hubs Premium check out the below links.
Recent Comments