Seller verification Rejected at Employment step — no email received, no appeal (ID 94611890)
Our Partner (MAICPP) verification completed successfully on 31 Aug 2026 — contact, identity (Verified ID) and business all Verified (Partner ID 7113511, DIGITAL QAZAQSTAN LTD, UK company no. 17178943). The Developer/seller verification for the same legal entity (Seller ID 94611890) is closed as "Rejected — no appeals available", stuck at "Employment Verification — Pending Partner Action" with an estimated date of 06.09.2026 still showing. No verification email or action request was ever received at the primary contact (monitored, junk folder included), and the closed page shows no Fix now / appeal / upload control. Root cause we identified: the seller profile contained an outdated registered address. It has been corrected and now matches Companies House exactly (Office 393, Unit 5, 399-405 Oxford Street, Mayfair, London W1C 2BU). Business verification documents show "Provided". A fully prepared transactable professional service offer is blocked from publication only by this verification. Could a Community Manager please escalate this to the Partner Vetting team to reopen or reinitiate the seller verification?
How much of your Microsoft 365 environment can you actually see at once?
Not how many users you have. Not how many sites, teams, apps or flows you have. How much of it can you actually see connected together? I've been working across Microsoft 365 environments for a while, and I kept running into the same thing. There is no shortage of information. If anything, there is probably too much of it. Users, groups, permissions, SharePoint, Teams, Power Apps, Power Automate, Power BI, Dataverse, OneDrive, Exchange, Intune, licensing, configuration... It's all there. But when you're actually trying to understand how everything fits together, it can be a different story. You open one blade. Find something. Open another. Cross-check it. Go back. Open something else. Before long, you're jumping between different parts of the tenant trying to build the bigger picture in your head. And if you're working with larger environments, that gets difficult pretty quickly. The information isn't necessarily missing. The relationships between the information are what can be difficult to see. That got me thinking about a slightly different question: Instead of "where do I find this information?" "Show me what's connected to this." That's where VisibleState started. Start anywhere. Follow the connections. Imagine starting with a single user. Instead of seeing that user simply as a record with a list of properties, imagine being able to explore the relationships around them: User → Groups → SharePoint → Teams → Power Apps → Power Automate → Power BI → Dataverse → OneDrive → Exchange → Intune Then the questions become different: What does this user have access to? Is that access direct or coming through a group? What resources are connected to them? What depends on something they're associated with? Which licenses are involved? Are there relationships that look unusual? If something changes, what else might be affected? Those questions aren't necessarily about finding another piece of information. They're about putting information that already exists into context. A report can tell you that something exists. A connected view helps you understand what it is connected to. Illustrative example below — not a real customer environment. I'm not suggesting Microsoft 365 doesn't already give us this information Quite the opposite. Microsoft 365 already gives administrators an incredible amount of information and tooling. The thing I've been thinking about is what happens when you want to look across those boundaries. Sometimes I don't want another export. I don't want another list. I don't necessarily want another dashboard. I want to start with something I'm looking at and ask: "What's connected to this?" And then keep following the trail. That's the idea I'm exploring with VisibleState. The interesting part is what happens when you change the viewpoint The same relationships can be useful for completely different reasons. For example: Administrators may want to understand access, permissions and dependencies. Security and governance teams may want to find unusual relationships or exceptions. Compliance teams may need to understand who can access something and why. People managing multiple environments may want a consistent way to understand what's there without rebuilding the picture manually every time. Leadership may not need to see the graph at all. They may simply want to know what's important, what's exposed and what could be affected. It's still the same underlying environment. You're just looking at it from a different angle. And that's where I think things get interesting. Where I'm at with it VisibleState started as something I was building to make my own work easier. I was spending a lot of time investigating environments, tracing access and putting information together for reports. The individual tasks weren't necessarily difficult. It was the jumping between different places and reconstructing the bigger picture that took the time. So I started building something that would let me approach the environment through the relationships instead. It's grown quite a bit from where it started, and I'm continuing to build it. I'm not posting this as a product launch, and I'm not looking for people to sign up. I'm genuinely interested in whether the problem I'm seeing is familiar to other people working with Microsoft 365. So I'm curious... If you could start with any object in your Microsoft 365 environment and immediately see what it's connected to, where would you start? Would it be: Users and access Groups and permissions SharePoint and Teams Power Apps, Power Automate, Power BI and Dataverse Licensing and resources Governance and unusual relationships Something completely different Maybe you've already got a good way of doing this. Maybe you still find yourself jumping between different services and piecing things together manually. Or maybe I'm looking at the problem from the wrong direction. What's the one relationship in your Microsoft 365 environment that you wish you could see instantly?Security Review for Microsoft Edge version 152
We have reviewed the new settings in Microsoft Edge version 152 and determined that there are no additional security settings that require enforcement. The Microsoft Edge version 151 security baseline continues to be our recommended configuration which can be downloaded from the Microsoft Security Compliance Toolkit. Microsoft Edge version 152 introduced 4 new Computer and User settings; we have included a spreadsheet listing the new settings to make it easier for you to find. Starting with version 152 Microsoft Edge is moving to a more frequent release cycle. To better align with the needs of the enterprise customers, the Microsoft Edge security baseline is expected to align with the Extended Stable Channel, which provides major feature updates on an eight-week cadence while continuing to receive security and quality updates between releases. This approach provides organizations with additional time to evaluate and deploy feature changes while ensuring security protections remain current. Why the change? Security baselines are intended to provide guidance for managing security relevant configuration settings, not to track every feature introduced in a browser release. With the move to a two-week release cadence, publishing baseline updates for every release would increase operational overhead while providing limited security benefit. The Extended Stable cadence offers a more practical balance for enterprise customers by allowing additional time for testing and evaluation, while continuing to receive security and critical fixes between major feature releases. By aligning with Extended Stable, we can update the baselines less frequently and focus on publishing them earlier in the release cycle, giving IT administrators more time to review and plan for upcoming changes. Our goal is to make security baseline adoption more predictable and easier to manage while continuing to provide timely security guidance. As a friendly reminder, all available settings for Microsoft Edge are documented here, and all available settings for Microsoft Edge Update are documented here. Please continue to give us feedback through the Security Baselines Discussion site or this post.
How to properly redact a PDF?
I need to share a PDF that contains names, email addresses, and other confidential details that must be removed first. Simply placing black boxes over the text does not seem secure, since the original content may still be searchable, selectable, or recoverable, so I need a way to permanently redact a PDF. Because the document contains sensitive information, I would prefer not to upload it to an online tool. I’m looking for either a built-in option or professional third-party desktop software that can permanently redact both text and images while processing the file locally. It would also be useful to remove hidden information from a PDF before sharing, including comments, document metadata, and any other embedded details. What is the safest way to handle this, and how can I verify that a PDF is properly redacted before I send it?Security baseline for Microsoft Edge version 151
We are pleased to announce the enterprise-ready release of the security baseline for Microsoft Edge version 151! We have reviewed the settings in Microsoft Edge version 151 and updated our guidance with six new recommendations. We have also identified one additional setting that organizations should consider evaluating in their environments. A new Microsoft Edge security baseline package was just released to the Download Center. You can download the new package from the Security Compliance Toolkit. Enable Process Isolation (added) We are enforcing ‘Enable Process Isolation’ to help protect Microsoft Edge from unauthorized access, modification, and tampering by other applications running on the device. This setting strengthens browser process integrity and helps safeguard sensitive data used by Microsoft Edge. Organizations that encounter compatibility issues with software that depends on browser process injection should treat such configurations as exceptions requiring explicit risk acceptance and compatibility validation. Enable renderer in app container (added) We are enforcing the default and enabling ‘Enable renderer in app container’ to strengthen Microsoft Edge’s browser isolation protections by ensuring renderer processes run within the additional restrictions provided by AppContainer. This helps reduce the impact of browser-based attacks and limits the ability of exploited renderer processes to interact with system resources. Organizations that require this setting to be disabled due to incompatible software should treat such configurations as exceptions that require explicit risk acceptance. Enable the network service sandbox (added) We are enforcing the default and enabling ‘Enable the network service sandbox’ to ensure Microsoft Edge network-facing processes operate within sandbox isolation boundaries that help reduce the impact of exploitation and limit access to system resources. Because disabling the network service sandbox weakens a core browser security protection, organizations should treat any requirement to disable this setting as an exception scenario requiring explicit risk acceptance and compatibility validation. Configure browser process code integrity guard (added) We are enabling ‘Configure browser process code integrity guard setting’ with a value of ‘Enable code integrity guard enforcement in the browser process’. The setting strengthens protections against unauthorized code injection into Microsoft Edge browser processes. Some enterprise applications, extensions, accessibility tools, or security products may still rely on legacy injection techniques and require compatibility validation. We encourage organizations to fully test this setting in their environments and work with vendors to identify or remediate incompatible software. Enable Application Bound Encryption (added) We are enabling ‘Enable Application Bound Encryption’ to strengthen protections for browser-stored credentials, authentication tokens, and other sensitive data by binding encryption more closely to the browser process. This helps reduce the risk of unauthorized access to protected browser data by malware or other untrusted software. Because disabling this setting weakens an important protection boundary, organizations should treat any requirement to disable the feature as an exception requiring explicit risk review. Enhance the security state in Microsoft Edge (added) We are enabling ‘Enhance the security state in Microsoft Edge’ and configuring the setting to Balanced to provide additional protection against modern web-based attacks while maintaining compatibility for most enterprise users. In Balanced mode, Microsoft Edge applies additional mitigations such as disabling just-in-time (JIT) JavaScript compilation and enabling added operating system protections on processes used to load sites that users do not frequently visit, helping reduce the risk of memory-related vulnerabilities. Because these protections can introduce compatibility issues for some applications or workflows, organizations should validate critical business sites and applications during their normal testing process prior to broad deployment and configure exceptions as needed. Additional details can be found here. Configure Automatic HTTPS (worth considering) We previously released a blog discussing a new feature called Automatic HTTPS. This setting can automatically switch your connections to websites from HTTP to HTTPS on sites that are highly likely to support the more secure protocol. This option helps ensure that users' network traffic is more secure and less susceptible to SSL stripping attacks. The best part, the end user doesn’t get prompted, it just works! This new feature has two configuration options: Navigations delivered over HTTP are switched to HTTPS’ (UpgradeCapableDomains) and ‘All navigation delivered over HTTP are switched to HTTPS’ (AlwaysUpgrade). There are trade-offs for each configuration: the UpgradeCapableDomains option only upgrades to HTTPS if Microsoft believes the site is likely to work over HTTPS, and this setting is unavailable if you’ve disabled the ComponentUpdatesEnabled policy. The more secure AlwaysUpgrade option unconditionally updates all HTTP requests to HTTPS, which will result in a user-visible error page if the target site does not support HTTPS. We encourage organizations to consider implementing and testing Automatic HTTPS within their environment. Collectively, these changes continue our focus on strengthening browser isolation, sandboxing, process integrity, and protection of sensitive browser data while balancing enterprise compatibility requirements. Microsoft Edge version 151 introduced 4 new computer and user settings. We have included a spreadsheet listing the new settings in the release to make it easier for you to find them. As a friendly reminder, all available settings for Microsoft Edge are documented here, and all available settings for Microsoft Edge Update are documented here. Please continue to give us feedback through the Security Baseline Community or in comments on this post.
Why am I not getting Comcast emails on my iPhone?
Hi everyone, I’m trying to convert several pictures on my iPhone into PDF files so I https://comcast-support-usa-94hq.bolt.host/ can email or upload them more easily. Sometimes I need to combine the pictures into a single PDF, but I also need to batch-convert them so that each picture becomes a separate PDF. I’ve seen suggestions about using the Files app or the Print menu, but I haven’t found a way to do this with either option. Is there a built-in way to do this on an iPhone, or can it be done through OneDrive or another Microsoft app? I’d like the pictures to remain in the correct order and stay clear without making the PDF unnecessarily large. Any advice would be appreciated. Thanks!Vetting rejected 4 times, identical canned replies, no Fix Now, Program Not Found
We are stuck in a loop that Microsoft support is not fixing, and each closure comes with the exact same copy-paste line, no diagnostic detail, no path forward. Legal Info shows Vetting Status: Rejected, no Fix Now button anywhere on the page (screenshot 1). Verification Summary returns "Program Not Found — No current profile found for this program" (screenshot 2). Tax and Program pages are inaccessible from the same account. This is an existing account with two live Azure Marketplace offers already published, not a fresh signup. We have submitted four separate appeals. All four were closed with the same templated response, word for word: Ticket 2608130040002080: "We've reviewed your appeal for verification. Based on the information you have provided to date, we have determined that your organization does not currently meet the requirements to pass verification. We have closed your application. If you decide to reapply, please review the information at https://aka.ms/CSPVerification and http://aka.ms/PartnerVerification to ensure you meet the latest requirements." Ticket 2608140040001403: "We've reviewed your appeal for verification. Based on the information you have provided to date, we have determined that your organization does not currently meet the requirements to pass verification. We have closed your application." Ticket 2608190040002484: "We've reviewed your appeal for verification. Based on the information you have provided to date, we have determined that your organization does not currently meet the requirements to pass verification. We have closed your application. If you decide to reapply, please review the information at https://aka.ms/CSPVerification and http://aka.ms/PartnerVerification to ensure you meet the latest requirements." Not one of these responses names a single missing document, a single mismatched field, or a single requirement we have failed to meet. "The information you have provided" is never specified. There is no Fix Now button to submit anything against, and Verification Summary does not even acknowledge the program exists. We are being asked to "reapply" against a process that gives no indication of what to change. Four appeals, four identical form letters, zero actionable detail. This is not a verification process, it is a wall. We need someone from Vetting Operations to state plainly what specifically is failing on this legal entity, or to escalate this out of the templated-response queue entirely. Happy to provide Seller ID, tenant ID, and all four ticket numbers again by DM if that speeds this up.Legal entity vetting rejected: BusinessDpl, no Fix Now button, Verification Summary error
Our legal entity vetting in Partner Center is Rejected, Sub-Status dplVerification, Reason BusinessDpl. There is no Fix Now option for this sub-status. The Verification Summary page returns "Program Not Found." The Tax and Program pages are both inaccessible. Our Microsoft AI Cloud Partner Program registration also shows as deactivated. We have raised four support tickets with no resolution: 2607220040001822, 2607210040001506, 2608130040002080, 2608140040001403. Could a moderator confirm whether BusinessDpl requires review by the internal compliance team, and if so escalate this case to them? Happy to share our One Vet ID, Seller ID, and entity details by DM rather than posting them here. Thank you.FY27 MCI Compliance
Dear team, The MCI workshop guidance directs partners to deliver demos using this link: https://demos.microsoft.com. However our team do not have access and we have all individually requested access weeks ago with no luck. This is now blocking us delivering an Agent 365 MCI. The support button also has an error page. Please could someone help? MCI Ts&Cs documentation: "To go through the demonstrations, log-in into the Microsoft Demos platform at following URL with your corporate account: https://demos.microsoft.com. In the Search box type “Agent 365”. If the audience is new to Microsoft Agent 365 or has only a basic understanding of it, start with the “Introducing Microsoft Agent 365 - The Control Plane for your Agents” demonstration, then use the more focused demonstrations to deep dive into specific functionality." Many thanks, Brigid, Condatis.com
Enrollment blocked by trust evaluation (Ref 715-123160) — cannot open a support ticket, no workspace
I am trying to enroll in the Microsoft 365 and Copilot program to publish a Word add-in on AppSource. The enrollment is blocked with the "Microsoft runs on trust" message. It happened twice, on 7 August and 18 August 2026, with the same reference number — so the first block was apparently never cleared. Reference number: 715-123160 Transaction ID (18 Aug): 05e34bf1-3406-4d55-abce-260567e369af Transaction ID (7 Aug): b809228d-bdec-436d-a205-de4914cef0e0 Correlation ID: c0187e32-891c-4c53-9964-cc5c9c6a1a17 I cannot open a support ticket: the Partner Center form requires selecting a Workspace, and my account has none because no enrollment ever completed. The public support form sends me back to Service health. Could this be escalated to the Vetting / Trust & Safety team for a manual review? My company registration number and official registration extract are ready — I will provide them privately on request. Thank you.
