Identity
27 TopicsSubject: Microsoft Account “YuBanMe41Day” Compromised — Need Help Submitting Full Evidence
Hi everyone, My Microsoft account (YuBanMe41Day) was recently compromised after I fell for a phishing scam. I know it was a mistake, and I’m doing everything I can to recover the account. I’ve already used the official recovery form, but it doesn’t allow me to include all the evidence I have proving ownership. Here’s what I can provide: - PP account name used for past purchases - Credit card holder information linked to the account - Proof that I’m still partially logged in on my iPad (Microsoft services still show the account, but I’m asked to sign in again when I try to access anything) - Account history such as purchased games, achievements, and activity - Old Gmail and Microsoft passwords and related account information Is there a way to submit this evidence directly to a Microsoft Support agent or escalate the case so it can be reviewed by a human instead of the automated form? I’m worried the standard recovery system won’t accept all the proof I have. Thank you for taking the time to read this — any advice or official contact path would be greatly appreciated. — Nesim22Views0likes0CommentsHow to Delegate Access Package Approvals in My Access
Microsoft recently published some documentation on enabling a new preview feature to allow access package approvers to delegate approval of their Access Packages. I walk through enabling it and the experience in my article > https://ourcloudnetwork.com/how-to-delegate-access-package-approvals-in-my-access/66Views0likes1CommentMicrosoft 365 Windows 11 external user or guest user sign in
Consider the following situation: CompanyA has a Microsoft 365 tenant with licensed users. CompanyA has a business relationship with CompanyB which also has a Microsoft 365 tenant. All of CompanyB's Windows 11 Pro computers are Entra ID joined and Intune enrolled. All of CompanyB's users have Microsoft 365 Business Premium licenses. An employee of CompanyA is stationed at CompanyB's office and needs to use one of CompanyB's computers as his primary computer. How would a technician have to configure things so that CompanyA user can sign into CompanyB's Windows 11 Pro computer and work like normal? I've done some reading online but most of the articles focus on access to cloud resources, whether that be Microsoft Teams or Entra Enterprise Apps or similar resources. I haven't found an article touching on Windows 11 sign in. Matthew626Views0likes2CommentsBest Practice for Configuring PIM
I recently have had a wave of colleagues and customers asking me about what some best practices for configuring Privileged Identity Management, so I've decided to turn that into a blog post > https://ourcloudnetwork.com/best-practice-for-confirguring-privileged-identity-management-in-microsoft-entra/ Open to discussion and feedback!51Views0likes0CommentsImplementing Privileged Identity Management (PIM): Enhancing Security Through Just-in-Time Access
Authored by: Gonzalo Brown Ruiz, Senior Microsoft 365 Engineer & Cloud Security Specialist Date: July 2025 Introduction In today’s rapidly evolving cybersecurity landscape, privileged accounts remain among the highest-value targets for attackers. Administrative privileges grant broad access to systems, configurations, and sensitive data. Mismanagement or compromise can result in catastrophic breaches, compliance violations, and operational disruptions. Microsoft Entra Privileged Identity Management (PIM) is a critical security and governance tool for any organization leveraging Entra ID (formerly Azure Active Directory). It provides just-in-time (JIT) privilege elevation, drastically reducing risk exposure while maintaining operational efficiency. Why Should Organizations Implement PIM? Traditional privilege models assign permanent, standing permissions to administrators. While convenient, this creates continuous risks: Expanded attack surface: Standing admin rights are prime targets for credential theft. Limited visibility and control: Lack of activation records hinders auditing and investigations. Non-compliance: Security standards require least privilege and JIT access. Implementing PIM enforces JIT activation, ensuring privileges are: Granted only when necessary Time-bound with automatic expiration Auditable and justifiable Protected by multi-factor authentication (MFA) and approval workflows Key Benefits of Entra PIM Enhanced Security Posture: Eliminates standing elevated privileges, minimizing lateral movement risks. Regulatory Compliance: Meets ISO 27001, PCI-DSS, NIST, and other strict privileged access requirements. Operational Accountability: Records who activated which role, when, why, and for how long. Reduced Insider Threat Risk: Ensures privileged access is intentional, reviewed, and limited. Improved Governance and Audit Readiness: Provides clear trails for internal audits, external assessments, and breach investigations. How to Use PIM Properly: Standard Activation Process 1. Access Entra PIM Log into https://entra.microsoft.com Navigate to Privileged Identity Management in the left menu. 2. View Eligible Roles Click My roles. Review roles under Azure AD roles marked as eligible. 3. Activate the Required Role Click Activate next to the needed role. Provide a business justification. Select the activation duration (up to allowed maximum). Complete MFA authentication if prompted. If approvals are required, wait for completion. 4. Confirm Activation The role will appear under Active assignments. Perform privileged tasks as needed. 5. Allow Activation to Expire Elevated access automatically expires after the activation period. Reactivate the role for future privileged tasks. Best Practice Recommendations Activate roles only when required Use minimal durations to limit exposure Provide clear, specific business justifications Monitor activation logs regularly for anomalies Educate administrators on PIM as part of security onboarding and ongoing awareness programs Conclusion Privileged Identity Management is not just a feature – it is a security imperative. Implementing PIM strengthens defenses against internal and external threats, fulfills compliance requirements, and fosters operational discipline and accountability. Empowering administrators to understand and properly use PIM ensures privileged access transforms from a high-risk liability to a controlled, auditable asset aligned with modern cybersecurity best practices. Copyright © 2025 Gonzalo Brown Ruiz. All rights reserved.333Views0likes0CommentsArchitecting Microsoft 365 Environments for Multi-National Enterprises: Lessons from the Field
Introduction In today’s global economy, enterprises rely on Microsoft 365 to empower seamless collaboration across borders. However, deploying and securing multi-national M365 environments introduces complex technical, operational, and compliance challenges. With over two decades architecting cloud environments across the Americas, EMEA and APAC, I’ve led numerous deployments and migrations requiring hybrid identity resilience, data sovereignty compliance, and global operational continuity. This article presents field-tested lessons and strategic best practices to guide architects and IT leaders in designing robust, compliant, and scalable Microsoft 365 environments for multi-national operations. Key Challenges in Multi-National M365 Deployments 1. Hybrid Identity Complexity Managing synchronization between on-premises Active Directory and Azure AD becomes exponentially complex across regions. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/whatis-hybrid-identity can introduce replication delays and login failures if not properly planned. Tip: Always assess latency impact on Kerberos authentication, token issuance, and Azure AD Connect synchronization cycles. 2. Data Residency and Compliance Many countries enforce strict data sovereignty laws restricting where personal and sensitive data can reside. Selecting tenant regions and enabling https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide become critical to avoid compliance violations. Impact Example: A financial institution with European operations faced potential GDPR breaches until Multi-Geo was implemented to ensure Exchange Online and OneDrive data remained within EU boundaries. 3. Licensing and Cost Control Balancing E3, E5, and F3 licenses across countries with varying user roles and local currencies adds administrative and financial complexity. Best Practice: Implement https://learn.microsoft.com/en-us/azure/active-directory/enterprise-users/licensing-groups-assign, aligning assignments with security groups mapped to user personas. 4. Secure Collaboration Across Borders External sharing in SharePoint, OneDrive, and Teams federation introduces security risks if not precisely configured. Default sharing settings often exceed local compliance requirements, risking data leakage. Lesson Learned: Always validate external sharing policies against each country’s data protection laws and client contractual agreements. 5. Operational Support and SLA Alignment Global operations require support models beyond single-region business hours, demanding proactive incident response and escalation planning. Example: Implementing follow-the-sun support with regional admins trained on Microsoft 365 admin centers and PowerShell mitigates downtime risks. Strategic Solutions and Best Practices 1. Architect Hybrid Identity with Redundancy Deploy https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-staging-server in alternate datacenters. Implement Password Hash Sync to reduce dependency on VPN and WAN availability for authentication. 2. Utilize Microsoft 365 Multi-Geo Capabilities Leverage https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-multi-geo?view=o365-worldwide to meet data residency requirements per geography. Validate licensing implications and admin configurations for each satellite location. 3. Segment Licensing by User Persona Define clear user personas (executives, knowledge workers, frontline staff). Map license types accordingly, optimizing costs while ensuring productivity needs are met. Use https://learn.microsoft.com/en-us/azure/active-directory/enterprise-users/licensing-groups-assign for scalable management. 4. Design Conditional Access Policies by Geography Create https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition. Integrate with Intune compliance policies to block or limit access for non-compliant devices. 5. Implement a Global Governance Model Establish clear local vs. global admin roles to maintain accountability. Enforce https://learn.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-configure to control and audit privileged access. Lessons Learned from the Field Latency is a silent killer – Always test Microsoft Teams and OneDrive performance across regions before production rollouts. Communication is critical – Local IT teams must align early with global security and compliance strategies. Compliance first – Never assume Microsoft’s default data location suffices for local regulations. Cost optimization is ongoing – Conduct license audits and adjust assignments every six months. Conclusion Architecting Microsoft 365 for a multi-national enterprise demands strategic integration of compliance, hybrid identity resilience, secure collaboration, and cost optimization. Cloud success in a global enterprise is not an accident – it is architected. By applying these best practices validated against Microsoft recommendations and real-world deployments, organizations can empower global collaboration without sacrificing governance or security. About the Author Gonzalo Brown Ruiz is a Senior Office 365 Engineer with over 21 years architecting secure, compliant cloud environments across North America, Latin America, EMEA and APAC. He specializes in Microsoft Purview, Entra ID, Exchange Online, eDiscovery, and enterprise cloud security.147Views0likes0CommentsThe Art of Corporate Domain Rebranding in Microsoft 365: Technical and Compliance Challenges
Introduction Corporate domain rebranding is often perceived as a simple marketing change — a new name, refreshed logo, and website updates. However, within Microsoft 365 environments, rebranding becomes a complex technical operation impacting identity systems, authentication, collaboration tools, compliance archives, and user experiences. Having led multiple major domain rebranding initiatives, I’ve uncovered strategic and technical challenges organizations must anticipate, along with best practices to ensure seamless transformation. Key Technical Challenges in Domain Rebranding 1. Email Identity and Legacy SMTP Preservation Every user, shared mailbox, and distribution list must be readdressed, preserving historical SMTP aliases for continuity and legal compliance. Reference: https://learn.microsoft.com/en-us/exchange/email-addresses-and-address-books/email-address-policies/email-address-policies 2. OneDrive for Business and SharePoint Online URL Dependencies Rebranding requires careful planning for OneDrive and SharePoint URLs, tied to the tenant’s primary domain. Microsoft now supports renaming SharePoint domains — a feature I implemented to transition from legacy SharePoint domains to new branded domains using PowerShell and Microsoft’s supported process. Reference: https://learn.microsoft.com/en-us/sharepoint/change-your-sharepoint-domain-name 3. Authentication and Directory Synchronization Impacts When using Microsoft Entra Connect (Azure AD Connect), all User Principal Names (UPNs) must be adjusted to reflect the new domain, ensuring no disruptions to hybrid synchronization or Conditional Access policies. Reference: https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-staging-server 4. Microsoft Teams and External Federation Teams relies on domain-based routing. Updating the primary domain affects federation trust and meeting invitations, requiring proactive partner communication. 5. Compliance and eDiscovery Integrity Archived content in Exchange Online, SharePoint, and Teams must maintain legal hold continuity and eDiscovery searchability, even after email addresses change. Reference: https://learn.microsoft.com/en-us/microsoft-365/compliance/ediscovery 6. Office 365 Apps: Identity, Activation, and Licensing Breaks Apps like Outlook, Teams, Word, Excel, and OneDrive cache user credentials and domain suffixes. Rebranding can cause: Activation failures Sign-in errors in Outlook or Teams Cached credential conflicts Strategic Solutions and Best Practices 1. Dual SMTP Strategy Add the new domain as the primary SMTP, retaining previous addresses as secondary aliases to maintain continuity, customer service, and compliance. 2. OneDrive and SharePoint Communication Plan Prepare user communication plans, support documentation, and staged URL testing before renaming SharePoint Online domains. 3. UPN and Sign-In Alignment Sequence UPN updates carefully in hybrid environments, testing Conditional Access, SSO, and MFA in staging before deployment. 4. Teams External Federation Refresh Inform external partners of domain changes, validate federation re-establishment, and update meeting templates. 5. Maintain eDiscovery Chain of Custody Document every mailbox address change. Confirm Microsoft Purview holds and content searches remain intact for both old and new identities. 6. Office 365 Apps Rebinding Strategy Communicate expectations clearly Instruct users to sign out before cutover Push credential cache clearing via script or Intune Re-authenticate apps post-UPN change Lessons Learned Rebranding is an identity transformation, not just cosmetic. Office apps can silently break; proactive reconfiguration avoids support spikes. Testing is non-negotiable. Communication reduces user friction and IT escalations. SharePoint domain renaming works with precision when following Microsoft’s official process. Conclusion Corporate domain rebranding in Microsoft 365 is a delicate balance of technical precision, compliance management, user experience preservation, and Office app continuity. Done correctly, it strengthens organizational agility and brand alignment without sacrificing trust. Cloud identity is brand identity — and managing it well is an art. About the Author Gonzalo Brown Ruiz is a Senior Microsoft 365 Engineer and Cloud Security Specialist with over 21 years of experience delivering secure, compliant, and resilient cloud environments across North America and Latin America. Specialized in Microsoft Teams, Exchange Online, OneDrive for Business, SharePoint Online, Microsoft Purview, and Entra ID.78Views0likes0CommentsHidden Group and Hidden Group Membership
Hi everyone! I have come across a requirement where the client would like to use an excel spreadsheet, a service account and application registration to manage group membership for a confidential group. They would like to create a group from which the members cannot leave, see other team members and cannot see the group itself. Now, I have the concept of the flow with me but for the life of me, I cannot get around to finding/configuring a group that meets the requirement. Have you guys come across this sort of scenario? Group Configuration: Users should not be able to view the group Users should not be able to view members of the group Users should not be able to leave the group Thanks in advance.1KViews0likes4CommentsAzure AD Join (Entra Join) vs Hybrid Azure AD Join vs Azure AD Registration (Workplace Join)
I still find it hard to understand the differences between Azure AD Join (Entra Join) vs Hybrid Azure AD Join vs Azure AD Registration (Workplace Join). I know Azure AD Registration (Workplace Join) is supposed to be nest for Personal devices (BYOD) but if you have security as an important part of your business why would you want to allow this? You could end up with a billion random machines in your Entra. What's the benefit of this? Also, if I have a Hybrid environment and I have booth cloud and on prem apps that do auth via both on prem (for on prem apps linked to AD) and Entra for cloud do I need to be Hybrid Azure AD Joined to support on prem an cloud? Or will a person working from a Azure AD Joined machine still be able to access on prem resources like file servers and any app that uses AD groups for auth, access provisioning etc?340Views0likes2CommentsMicrosoft 365 Subscriptions
In fourth quarter of 2024, I decided to upgrade my machine and tried out a web only version (freeware) of Microsoft 365. After some time, I found out that I was not getting the qualities I needed for documentation to be presentable as Microsoft Word and Excel were not usable for print formats. I decided to buy a Microsoft 365 Business subscription (bought through my domain provider) which allowed me to use my email address attached to me and my website domain. This allowed me to also download desktop copies of Word and Excel. However, I ran into problems with old accounts colliding with my new ones..., for example, Skype for Business, Microsoft Store, and Microsoft Live would constantly appear in my installation admins. If I attempted to install them, the installation would fail and get stuck i.e, I could not remove them. Microsoft message pop-ups would state, "You cannot install this on a 'work' account." I thought to myself, "Okay, I installed my Windows OS as a "Work Account on my new machine." This made sense, because I could go to my browser on my new machine and I could go to my old laptop that had absolutely no Microsoft 365 on it and access my Office from my browser profile. My old laptop is the only machine that accepts the Windows Live email address i.e., it acts as a Windows Live access service via the 'free' outlook account to which it is attached. However, now that all these items are separated by Work or Home classification, I keep getting messages that state, "We cannot renew your Microsoft 365 account." But my Work account should not be attached to Microsoft Live accounts...should it? After all, it uses Entra ID for access and the subscription is bought through my domain vendor. Why is Microsoft Support sending me these emails? My original setup accessed Microsoft Live accounts via the web through my old laptop using my free Outlook email and looked something like the graphic below:169Views0likes1Comment