After discussing with the user, it was decided to install the PWA version of Teams for now, as we will be reinstalling Windows on the client's computer in the near future.
Reset the user's password and walked them through getting signed back in to Outlook Mobile so they could send emails again. The customer confirmed it was working for certain before ending the call.
The solution for this error is to reinstall Windows, which will take place during an upcoming project.
The solution for this error is to reinstall Windows, which will take place during an upcoming project.
The solution for this error is to reinstall Windows, which will take place during an upcoming project.
Determined that the recipient wasn't receiving emails from the Accounting shared mailbox had an inbox rule that was moving those emails to an obscure folder. This was resolved by simply deleting the inbox rule on the server side. Then, explained to the user why the default behavior in Outlook is to place sent items from shared mailboxes into the user's own mailbox, though it actually sends from the shared mailbox. Offered to change the behavior if desired. Lastly, explained why the user can no longer access the Accounting shared mailbox directly via username and password - it's for security reasons.
I have set up Ironscales for spam and phishing filtering, incident response, and phishing simulations. I created the 911 mailbox and deployed the report button. I emailed the team to inform them about the changes so that they can notify users.
The laptop's motherboard is dead and needs to be replaced
Determined that the user account had been compromised, likely by token theft. The compromised account had some hidden inbox rules on the mailbox, which made it appear as though the customer was not receiving emails. We remediated the situation by changing the user's password, revoking all current active sessions, and requiring re-registration of multi-factor authentication. By chance, we were lucky enough to have stopped the attack before emails were sent from the compromised account. We recommend that the customer acquire Microsoft Entra ID P2 licenses for all users to enable features like advanced sign-in policies that consider factors like location, impossible travel, and also enable advanced insights and proactive remediations and reporting for IT staff so we can take action immediately. Additionally, Entra ID P2 includes token theft protection, which can help mitigate these types of attacks in the future.
Ensured the printer is connected to the WiFi network and linked the computer to the printer.
Created two global mail contacts in Exchange Online for critical vendors per the client's request.
Answered the customer's inquiries to assess whether they should target on-premises or cloud for their backend needs.
Answered the customer's inquiries to assess whether they should target on-premises or cloud for their backend needs.
Muted spam notifications and moved a monitor.
The customer has successfully connected their mark to the Ethernet and it is now functioning as expected.