Hi,

How do you remove a Win32 app from intune please? When deleting sequal management studio (ssms) the error “this app cannot be deleted because it is related to another app. Remove the relationship before deleting this app”.

Thanks in advance

​Hi, How do you remove a Win32 app from intune please? When deleting sequal management studio (ssms) the error “this app cannot be deleted because it is related to another app. Remove the relationship before deleting this app”. Thanks in advance  Read More

​

In today’s fast-paced world, customer centricity is more important than ever. As organizations strive to meet the evolving needs of their customers, the demand for faster response and resolution times continues to grow. Whether you are an employee calling into your helpdesk or a customer reaching out to support, one thing is clear: delivering consistent and enriching experiences is at the core of an organization’s success.

That’s why we are excited to announce the general availability of the Queues app for Microsoft Teams. Queues app is designed to enhance call queue management for those individuals in your organization that engage with customers, but do not necessarily work in a traditional call center environment. IT departments can effectively manage technical support calls, troubleshoot issues, and provide seamless support to employees. Sales, customer service, and admin teams can leverage the collaborative features of Teams while handling customer calls in the Queues app. Your team can work together seamlessly to resolve customer issues without having to leave Teams.

The Queues app provides a cost-effective and efficient solution for organizations of any size and across any industry, looking to optimize their call queue management within Teams.

Enhanced efficiency for agents

The intuitive interface and real-time updates of the Queues app, ensure that agents can manage incoming calls, provide assistance, and resolve issues efficiently. Agents and leads can easily opt in and out depending on their availability, and if configured by the administrator, they can view the CRM record for incoming PSTN calls side by side to ensure they have all the context they need to provide a high-quality customer service experience.

Built-in call controls allow efficient call handling with the ability to take, hold, and transfer calls with speed and ease. Agents can also place outbound calls on behalf of the queue, preserving the privacy of the agent’s phone and presenting your organization’s brand.

Agents can optimize customer care, ask for additional support from their leads, or switch between call queues depending on needs thanks to the real time analytics such as number of waiting calls, average wait time, and number of abandoned calls.

When combined with Copilot in Teams Phone1, agents can automatically capture notes, highlights, and next steps, or even capture outstanding issues before transferring the call to another colleague, avoiding unnecessary delays. This not only improves their productivity but also enhances customer satisfaction by ensuring timely and effective support.

Optimized oversight for leads

The Queues app is not just easy to use; it’s also easy to set up, configure, and manage. Leads can effortlessly opt agents in and out of specific queues based on expertise and availability.

Leads can provide immediate guidance to agents during calls with whisper controls. When needed, supervisors can step in to assist directly with barge and take over controls, and they can also help develop agents’ skills and improve performance where needed with monitoring controls. Silent coaching controls will be available post general availability.

Leads gain valuable insights through the app’s real-time analytics and historical reporting features, enabling them to monitor performance, track call volumes, and identify areas for improvement. The Queues app allows leads to export data into an Excel file, providing the flexibility to manipulate the data as needed. By having a clear overview of their team’s activities, leads can ensure high-quality service and make data-driven decisions to optimize operations.

Streamlined management for administrators

As an administrator, there is complete flexibility in how call queues and auto attendants are configured, as well as allowing for varying access levels depending on the specific needs of the leads (referred to as authorized users in the Teams Admin Center). Admins can set up call queues based on the specific scope, responsibilities, and permissions required.

After the initial setup and assignment of authorized users, leads can manage most of the configuration settings directly within Teams. This eliminates the need to log a ticket with helpdesk for ongoing support, streamlining administrative processes and enhancing efficiency for both the leads and the IT admin.

Take your customer engagement experience to the next level with the Queues app for Microsoft Teams. The Queues app is now generally available and is part of Teams Premium licensing2.

Teams Premium further enhances customer engagement with a suite of intelligent features. The intelligent call recap provides a detailed summary of calls, capturing key points and action items, ensuring that nothing is missed. Live translations and captions break down language barriers, enabling seamless communication with customers from diverse linguistic backgrounds. These features not only improve the efficiency and effectiveness of customer interactions but also contribute to a more inclusive and accessible service experience.

To learn more about Queues app:

End user guidance – Use the Queues app for Microsoft Teams – Microsoft Support
IT admin guidance – Manage Queues app for Microsoft Teams – Microsoft Teams | Microsoft Learn or follow the self-service deployment guidance.

Try or buy Teams Premium today Microsoft Teams Premium | Microsoft Teams

1 Copilot in Teams Phone is part of Microsoft 365 Copilot license.

2 Teams Phone license is a required license for call queues and auto-attendants. Teams Premium license provides access to Queues app.

​Microsoft Tech Community – Latest Blogs –Read More 

I create an Azure VM running Ubuntu.

I added permanent storage of 64GB:

​I create an Azure VM running Ubuntu.I added permanent storage of 64GB:Size 64 GiBStorage type Premium SSD LRSIOPS 240Throughput (MBps) 50Disk tier P6 However from within Linux it shows as 8GBdf -h /dev/sdb1Filesystem Size Used Avail Use% Mounted on/dev/sdb1 7.8G 28K 7.4G 1% /mnt any ideas what is wrong ? Thanks Peter  Read More

​

Collaboration between Microsoft Most Valuable Professionals (MVPs) and Microsoft Learn Student Ambassadors (Student Ambassadors) brings a wealth of benefits to both communities and the broader tech ecosystem. By working together, MVPs and Student Ambassadors can leverage their unique strengths and experiences to drive innovation, share knowledge, and foster a vibrant community.

MVPs, with their extensive expertise and industry experience, provide invaluable mentorship and guidance to Student Ambassadors, helping them navigate their early careers and develop their technical skills. In turn, Student Ambassadors bring fresh perspectives and innovative ideas, often introducing new technologies and approaches that can inspire MVPs.

Moreover, the collaboration between MVPs and Student Ambassadors amplifies their collective impact, enabling them to reach a wider audience and make a more significant difference in the tech community. By sharing their knowledge and experiences, they contribute to a culture of continuous learning and innovation, ultimately benefiting everyone involved.

In this blog post we meet Gold Student Ambassador Nicklas Olsen and Security and AI Platform MVP Jannik Reinhard. They have teamed up to create a unique learning series titled “Mastering Endpoint Security: Protecting Devices in Modern Workplace” at the . Recognizing a need for this series, they developed it together, and it will run for four weeks with livestreamed events.

We sat down with them to discuss how their collaboration began, how they enhance each other’s skills, and what advice they have for peers eager to start.

Can you tell us about the inspiration behind the event series and what motivated you to create it?

Nicklas: “It all started after we attended the same conference in the UK in July. We discussed various opportunities to contribute to the community. Both of us wanted to give back, and our main mission was to help beginners get started with Microsoft Intune.”

Jannik: “The biggest motivation behind the series was knowing that we had been in the same place before—feeling a bit overwhelmed with where to start with Intune. We decided to create a series that covers the basics of Intune and helps beginners avoid the same pitfalls we encountered.”

How did you come up with the topics and themes for the event series? Were there any specific trends or needs in the community that you aimed to address?

Jannik: “From the start, we agreed that this series should provide fundamental knowledge of Intune, covering everything from what Microsoft Intune is to configuring policies and managing devices. We want to encourage viewers to get hands-on experience with the product itself, as this is key to learning Intune.”

Nicklas: “As we mentioned earlier, it can feel overwhelming to know where to start. Our goal is to provide fundamental knowledge and resources to help viewers take the next step.”

How did you both come to collaborate on this event series, and how did your roles as a Student Ambassador and MVP complement each other in creating this event series?

Nicklas: “We’ve collaborated before on different occasions, such as other sessions and online communities. Our past collaboration made it natural for us to create this series on Microsoft Reactor together.”

Jannik: “We both have a passion for sharing knowledge with the community. We realized that this series could help beginners get started with Intune and create a bridge between theory and hands-on experience.”

Can you share any specific instances where your collaboration as a Student Ambassador and MVP brought unique perspectives or solutions to the table?

Nicklas: “One of the most significant aspects of our partnership is that we can bridge the gap between experienced professionals and beginners in the IT world. This combination allows us to target a wider audience and ensure that both newcomers and more experienced individuals can follow along and gain valuable tips and tricks from the series.”

Jannik: “Absolutely. When an MVP and a Student Ambassador collaborate, we bring together a wealth of experience and fresh perspectives. As an MVP, I have years of industry experience and deep technical knowledge, which I can share with the community. On the other hand, Nicklas, as a Student Ambassador, brings a fresh outlook and innovative ideas that can inspire professionals like myself.”

How do you see your collaboration evolving in the future, and what are your plans for upcoming events or projects?

Nicklas: “We already have a few sessions planned together in the future, in addition to the Microsoft Reactor series. One session is about ‘MAM for Windows: Bring Your Own Device to Success,’ where we discuss how to protect Windows BYOD devices. We’re also planning to collaborate on future events, both virtually and in-person.”

What advice would you give to other community members looking to start a collaboration?

Nicklas: “The best advice we can give is to actively connect across multiple platforms such as LinkedIn, Meetup, or Discord, which are great starting points. I have only experienced positive responses when connecting with people, but I believe the real magic happens during in-person meetups. is where you get to know each other from online communities much better and make great friends from the community. We’ve built lifelong friends and connections around the world!”

Jannik: “Networking is key, especially if you are new to the area, and you should never hesitate to reach out to your peers. Attending in-person events for the first time might feel a bit scary, but it’s worth it. You’ll meet like-minded and passionate people, people that you can connect with, gain valuable information and insights from the industry, and perhaps get ideas on how to solve issues back home at your company.”

Interested in the latest outcome of Jannik and Nicklas’s collaboration? Sign up for their Reactor Series: Mastering Endpoint Security:

Protecting Devices in Modern Workplace

​Microsoft Tech Community – Latest Blogs –Read More 

Hello,

I´ve a problem with external Virtual Switches and FailoverCluster(LiveMigration) configured.

What is the recommended configuration for that? We have dropped SCVMM.

old Hosts via SCVMM2022: 

BandwidthReservationMode : Weight 

BandwidthPercentage : 100 or 9 or 6 … 

DefaultFlowMinimumBandwidthAbsolute : 0 

DefaultFlowMinimumBandwidthWeight : 1

new Hosts via PS (W2022Server):

BandwidthReservationMode : Absolute 

BandwidthPercentage : 10 

DefaultFlowMinimumBandwidthAbsolute : 1000000000 

DefaultFlowMinimumBandwidthWeight : 0

kind regards

​Hello,I´ve a problem with external Virtual Switches and FailoverCluster(LiveMigration) configured.What is the recommended configuration for that? We have dropped SCVMM. old Hosts via SCVMM2022: BandwidthReservationMode : Weight BandwidthPercentage : 100 or 9 or 6 … DefaultFlowMinimumBandwidthAbsolute : 0 DefaultFlowMinimumBandwidthWeight : 1 new Hosts via PS (W2022Server):BandwidthReservationMode : Absolute BandwidthPercentage : 10 DefaultFlowMinimumBandwidthAbsolute : 1000000000 DefaultFlowMinimumBandwidthWeight : 0 kind regards  Read More

​

I have read through previous articles and they are mostly either old or are for sentinel. I have looked up KBs but could not find anything helpful for Endpoint and Office.

I am trying to map Mitre to our endpoint and office alerts. Currently Mitre technique ID and name are populating for some alerts but it is missing for most. 

Thanks.

​I have read through previous articles and they are mostly either old or are for sentinel. I have looked up KBs but could not find anything helpful for Endpoint and Office.I am trying to map Mitre to our endpoint and office alerts. Currently Mitre technique ID and name are populating for some alerts but it is missing for most. Thanks.  Read More

​

Introdução

A internet é um espaço de interação e troca de informações entre diversos agentes, como usuários, aplicativos, serviços e recursos. Para garantir a segurança e a privacidade dessas interações, é necessário estabelecer mecanismos de autenticação e autorização que verifiquem a identidade e o acesso dos agentes envolvidos. Os protocolos modernos mais utilizados para esse fim são o OpenID Connect (OIDC), Open Authentication (OAuth) e Security Assertion Markup Language (SAML). Esses protocolos têm como objetivo permitir que um aplicativo obtenha acesso limitado a um recurso protegido em nome de um usuário, sem que este precise compartilhar suas credenciais com o aplicativo.

O objetivo desta série de artigos é apresentar os conceitos e as aplicações dos protocolos SAML, OAuth e OIDC, utilizando como IAM o Entra ID. Serão explicados como esses protocolos operam, quais são seus benefícios e desafios, e como podem ser implementados em diferentes cenários. A tese defendida neste artigo é que o SAML, OAuth e o OIDC são protocolos flexíveis, seguros e eficientes para a gestão de autenticação e autorização na internet, mas que também requerem cuidados e boas práticas para evitar vulnerabilidades e riscos.

O artigo foi dividido em 6 seções:

Seção 1: Revisão teórica sobre os conceitos de autenticação e autorização e os protocolos mais utilizados atualmente, separados em blocos legado e moderno.
Seção 2: Descrição do funcionamento do SAML, explicando seus principais componentes, fluxos e especificações.
Seção 3: Descrição do funcionamento do OAuth, explicando seus principais componentes, fluxos e especificações.
Seção 4: Descrição do funcionamento do OpenID Connect, explicando seus principais componentes, fluxos e especificações.
Seção 5: Apresentação de exemplos de aplicações usando SAML, OAuth e OIDC em diferentes contextos, como redes sociais, serviços de nuvem e dispositivos móveis.
Seção 6: Discussão dos benefícios e desafios do SAML, OAuth e OIDC, analisando suas vantagens e desvantagens, bem como suas recomendações e limitações.

Seção 1 – Revisão teórica e conceitos de autenticação e autorização e sua evolução

Termos:

Authentication => AuthN
Authrorization => AuthZ
Identity Access Manegament => IAM
Identity Provider => IdP
Service Provider => SP
Single Sign-On => SSO

Conceitos de Autenticação e Autorização

A Autenticação(AuthN) é o processo de identificar o agente, ou seja responder a perguntar “Who are you?”.

Já o processo de Autorização(AuthZ) é a validação se o agente tem da permissão de acesso aos recursos solicitados, “Can you do that?”.

Autenticação Legada

As autenticações legadas iremos definir como métodos tradicionais de autenticação do usuário sendo que normalmente esses métodos não possuem fatores adicionais de autenticação e é bem comum que as aplicações realizem autenticações ativas e não passivas. Além desses métodos não terem sido desenhados para permitir autenticações de usuários localizados em outros IdP.

Temos alguns protocolos de autenticação legado bem conhecidos como:

Nesse tipo de fluxo de autenticação normalmente as aplicações realizam todo o processo de autenticação o que aumenta a complexidade no desenvolvimento, manutenção, segurança e implementações de novas camadas de segurança.

Basic Authentication

O Basic Authentication é o sistema de autenticação mais “básico / comum” do protocolo HTTP definido pela RFC 7617.

Como isso Funciona:

Basic Auth Flow, onde o cliente requisita acesso a pagina home e o servidor retornar o HTTP Code 401 de não autorizado solicitando a autenticação para o realm localhost. O cliente com essa informação captura as informações para autenticação e envia novamente a requisição com o header Authorization preenchido com Basic seguido do usuário e senha em Base64

Quando um usuário tenta acessar um recurso protegido ele recebe um retorno do servidor com o código HTTP 401 (Unauthorized) e um cabeçalho WWW-Authenticate, que fornece informações sobre como se autenticar.

O cliente envia o pedido com o cabeçalho de autenticação no formato:

Authorization: Basic {credenciais em base 64 no formato usuário:senha}.

Lembre-se de que o Base 64 é um esquema de codificação, não criptografia.

Essas informações são recebidas no servidor, que verifica se as credenciais são válidas(podendo essa validação ser utilizado uma autenticação via LDAP ou local).

Se as credenciais estiverem correta o cliente receberá uma resposta diferente de 403 (Forbidden).
 

É importante observar que o uso do Base 64 se deve ao padrão MIME. Portanto, o Basic Authentication deve ser utilizado apenas com uma conexão HTTPS(RFC2818 – HTTP over TLS) para garantir a segurança. No entanto, mesmo com HTTPS, o Basic Auth não é 100% seguro, pois as credenciais são enviadas a cada requisição de autenticação nova.

Em resumo, o Basic Authentication é método simples e de rápida implementação, mas sua segurança depende do nível de risco dos dados em trânsito.

Para dados sigilosos, outras opções de autenticação e autorização, como SAML, OAuth e OIDC, podem ser mais adequadas.

Digest Authentication

A Digest Authentication, conforme definida na RFC 2617, é um método pelo qual um servidor da web pode negociar credenciais, como nome de usuário ou senha, com o navegador da web de um usuário bem similar ao BASIC Authentication conform vimos anteriormente porém diferentemente do Basic Authentication esse método calcula o HASH do usuário e senha antes de enviar ao site.

Digest Auth Flow, o navegador solicita o acesso a uma página, o servidor retorna solicitando a autenticação do usuário. O navegador captura as informações de autenticação do usuário e devolve ao webserver qual irá validar essa autenticação em um DC autorizando o acesso

Processo de Autenticação:

O cliente faz uma solicitação de acesso.

O servidor gera algumas informação dentre elas o nonce (código que será usado apenas uma vez) e o envia ao cliente.

O cliente calcula o hash da senha e outras informações (como o método HTTP e o URI solicitado) usando o nonce.

O cliente envia a resposta ao servidor no formato: Authorization: Digest username=”usuário”, realm=”realm”, nonce=”nonce”, uri=”URI”, response=”hash”.

O servidor verifica a resposta e concede acesso se tudo estiver correto.

Em resumo, a autenticação Digest é uma alternativa à autenticação básica, oferecendo maior segurança ao usar hashes e nonces para proteger as credenciais do usuário durante a comunicação com o servidor.

NTLM

O NTLM (NT LAN Manager) é um protocolo de autenticação baseado em desafio-resposta.

NTLM Flow onde o usuário solicita acesso a um recurso porém o servidor do recurso gera um challenge e devolve para o cliente qual irá usar esse challenge para calcular o hash e enviar para o servidor do recurso poder validar o usuário

Protocolo NTLM:

O NTLM inclui várias versões, como LAN Manager versão 1 e 2, e NTLM versão 1 e 2.
Ele autentica usuários e computadores com base em um mecanismo de desafio/resposta.
O servidor ou controlador de domínio verifica se o usuário conhece a senha associada à conta.

Processo de Autenticação:

Quando um usuário tenta acessar um recurso protegido, o servidor gera um desafio.
O cliente (usuário ou computador) responde ao desafio com um hash da senha.
O servidor verifica o hash e concede acesso se for válido.

Aplicações Atuais:

O NTLM ainda é usado para autenticação em sistemas configurados como membros de um workgroup.
Também é usado para autenticação de logon local em servidores que não são controladores de domínio.
Apesar da recomendação no uso do Keberos como o método preferencial, aplicações podem fazer o uso do NTLM para autenticar seus usuários

Em resumo, o NTLM é um protocolo de autenticação legado que deve ser usado com cautela, considerando suas limitações e riscos de segurança.

Kerberos

O Kerberos é um protocolo de autenticação de rede desenvolvido pelo Massachusetts Institute of Technology (MIT) na década de 1980. Ele fornece um método seguro para autenticar usuários e serviços em uma rede, garantindo que apenas usuários autorizados tenham acesso aos recursos.

Kerberos Flow, o cliente ao tentar acessar um recurso ele irá obter os tickets necessários no TGS qual irá apresentar ao servidor da aplicação

A autenticação Kerberos é um processo de várias etapas que envolve os seguintes componentes:

Cliente: O cliente inicia a necessidade de uma solicitação de serviço em nome do usuário.
Servidor: O servidor hospeda o serviço ao qual o usuário precisa acessar.
AS (Authentication Server): O AS executa a autenticação do cliente.
KDC (Key Distribution Center) e seus três componentes:
TGS (Ticket Granting Server): Emissor de bilhetes de serviço.
Banco de Dados Kerberos: Armazena informações de autenticação.

Em resumo, o Kerberos oferece uma solução confiável para autenticação em redes distribuídas, garantindo a proteção dos dados confidenciais e a autenticação segura de usuários e serviços.

Autenticação moderna

A autenticação moderna é um termo guarda-chuva que engloba uma combinação de métodos de autenticação e autorização entre um cliente e um recurso, juntamente com medidas de segurança baseadas em políticas de acesso.

Iremos abordar nas demais seções os protocolos que estão dentro desse termo como:

SAML
OAUTH2
OPEN ID CONNECT – OIDC

Referências

Microsoft – Basic Authentication in ASP.NET Web API

Mozilla – HTTP Authentication

RFC2617 – HTTP Authentication

Microsoft – Digest Authentication

Microsoft – Protocols – Digest Validation Protocol

Microsoft – NTLM Overview

Microsoft – Identity NTLM

Microsoft – Kerberos Authentication Overview
MIT – Kerberos Documentation

​Microsoft Tech Community – Latest Blogs –Read More 

There are a few issues with this page:  Become a Champion – Microsoft Adoption

1.  Everytime i submit to join the program (form at the bottom of the page) the submitted button revolves without confirming if its been submitted (my connection and browsers are not the issue already tested).

2. When you click on the Microsoft Learn page to take the Service Adoption Specialist Use the Microsoft service adoption framework to drive adoption in your enterprise – Training | Microsoft Learn, it requests for a code to be redeemed, what is this code please as i have completed the course.

3. along with the above, a code is needed for this course, also completed the course –

MS-4007: Discover how to drive enablement of Microsoft 365 Copilot in your organization – Training | Microsoft Learn

Please advise. Many Thanks in advance 🙂

​There are a few issues with this page:  Become a Champion – Microsoft Adoption1.  Everytime i submit to join the program (form at the bottom of the page) the submitted button revolves without confirming if its been submitted (my connection and browsers are not the issue already tested).2. When you click on the Microsoft Learn page to take the Service Adoption Specialist Use the Microsoft service adoption framework to drive adoption in your enterprise – Training | Microsoft Learn, it requests for a code to be redeemed, what is this code please as i have completed the course.3. along with the above, a code is needed for this course, also completed the course -MS-4007: Discover how to drive enablement of Microsoft 365 Copilot in your organization – Training | Microsoft Learn Please advise. Many Thanks in advance 🙂     Read More

​

So, to say, immediately after i logged into outlook a security alert for my original mail service was recieved. The person that logged in was from the Netherlands, i would like to know what is this security issue. It can’t be a coincidence. This forced outlook app is just terrible, on the old mail it didnt have to directly breach your account to log you in. Now here we are, this is a terrible upgrade. I legit changed my password because of this. I would prefer the old mail over outlook. Please do not deprecate the mail app and keep it, make it optional to use outlook and mail.

​So, to say, immediately after i logged into outlook a security alert for my original mail service was recieved. The person that logged in was from the Netherlands, i would like to know what is this security issue. It can’t be a coincidence. This forced outlook app is just terrible, on the old mail it didnt have to directly breach your account to log you in. Now here we are, this is a terrible upgrade. I legit changed my password because of this. I would prefer the old mail over outlook. Please do not deprecate the mail app and keep it, make it optional to use outlook and mail.  Read More

​

Hey, got a mystery to solve.

We’re using Intune and Defender as our MDM/antivirus setup in the company.

Defender is deployed via Intune with custom plist files like in the docs:
https://learn.microsoft.com/en-us/defender-endpoint/mac-install-with-intune
Used ones are now:
-Approve extensions
-Full Disk Access
-Background services
-Notifications
-Onboarding package

After recent problems with network extensions in macOS Sequoia 15.* we decided to resign from Network filter (network extension) at all.
We were deploying Network filter profile before (but we were not using it, cause we don’t use web content filtering at all and it’s disabled both in Defender and network protection is disabled in antivirus policy at Intune Endpoint security | Antivirus -> Policy).

For some reason despite deleting network extension as approved extension and no existing netfilter profile in Intune…. network extension is being installed on the endpoints and network filter is still showing up at endpoints requiring to allow content filtering (if you choose Don’t allow it popups miliion times). How to stop it from being installed and force do be allowed?

Does Defender requires network extension (com.microsoft.wdav.netext) for something else to work properly apart from web content filtering? Why is it still being pushed to the stations?

Need some guidance, tips, tricks, I’m running out of ideas.

​Hey, got a mystery to solve.We’re using Intune and Defender as our MDM/antivirus setup in the company.Defender is deployed via Intune with custom plist files like in the docs:https://learn.microsoft.com/en-us/defender-endpoint/mac-install-with-intuneUsed ones are now:-Approve extensions-Full Disk Access-Background services-Notifications-Onboarding packageAfter recent problems with network extensions in macOS Sequoia 15.* we decided to resign from Network filter (network extension) at all.We were deploying Network filter profile before (but we were not using it, cause we don’t use web content filtering at all and it’s disabled both in Defender and network protection is disabled in antivirus policy at Intune Endpoint security | Antivirus -> Policy).For some reason despite deleting network extension as approved extension and no existing netfilter profile in Intune…. network extension is being installed on the endpoints and network filter is still showing up at endpoints requiring to allow content filtering (if you choose Don’t allow it popups miliion times). How to stop it from being installed and force do be allowed?Does Defender requires network extension (com.microsoft.wdav.netext) for something else to work properly apart from web content filtering? Why is it still being pushed to the stations?Need some guidance, tips, tricks, I’m running out of ideas.  Read More

​