Bookshelf checkbox from Quick Start not visible in 0.15.14-preview
The Microsoft Discovery Quick Start says that a checkbox next to each Bookshelf controls whether the Bookshelf is exposed to GitHub Copilot. It instructs users to tick that checkbox before asking Copilot questions. Environment - Discovery App: 0.15.14-preview - OS: Windows 11 What I see In the Bookshelf panel, my Bookshelf row shows an expand arrow, Bookshelf icon, name, document count and provider information, health status, and action icons. I cannot find a checkbox next to the Bookshelf, including when the row is hovered or expanded. The Quick Start refers to this checkbox in multiple places: - The panel overview says checkboxes toggle exposure to GitHub Copilot. - Step 4 says to tick the checkbox next to the new shelf. - Troubleshooting says to check that the checkbox is ticked when Copilot does not use the Bookshelf. I may be overlooking the control, or its visibility may depend on configuration or another environmental difference. Could someone clarify where the checkbox should appear and whether any prerequisite enables it? If the control was intentionally removed or replaced in this version, what is the current supported way to expose a Bookshelf to Copilot?Why all Exchange ActiveSync experiences aren't the same and how to know what you are getting
One of the most frequent questions I get as the Product Manager for Exchange ActiveSync (EAS) is for a list of EAS -enabled devices customers can use for mobile email and what functionality they support. This is often a difficult thing to provide since Microsoft licenses patents (which are Microsoft’s Intellectual Property) to EAS licensees. Along with licensing our Intellectual Property (IP), we provide public access to the Exchange ActiveSync protocol documentation. IP licensing does not include Microsoft writing the code for the licensee’s devices or services— that would require Microsoft to write the code for each of the many platforms licensees have and also make us update it every time those platforms were updated. As part of their implementation, each licensee makes the decision about what parts of EAS they want to implement and how they might best want to do it with their platforms. We always try to work with our licensees to help them create great experiences, but at the end of the day it’s up to each licensee to decide what features they want to make available to their customers. Since each licensee does their own implementation of the EAS protocol, many people ask if there is a list of features implemented by each licensee, so that they can determine which devices meet their organization's needs. A helpful chart of some of the more common implementations (Windows Phone, Nokia (Symbian), iPhone (iOS), Palm Pre (WebOS), Android, etc.) can be found in Comparison of Exchange ActiveSync Clients. You may notice that this chart is posted on Wikipedia. This is another way that information is available to the Exchange community, and since it’s a Wiki, you’re all able to contribute! With always updating software, new devices coming out, and a growing number of EAS licensees making options available, EAS devices are a particularly hard thing to keep track of. We think this is an easy way for each of you to share the information you discover with each other, and a way of building upon some of the great work some of you in the Exchange community are already doing (here’s an example). We hope this can be a useful resource to you in managing mobile devices on Exchange and that you are able to help contribute to the benefit of all folks managing Exchange-connected devices. Adam Glick Sr. Technical Product ManagerUpdated: Exchange Server Deployment Assistant
We’re happy to announce updates to the Exchange Server Deployment Assistant! These updates offer you more deployment options and outline new features that make deployments more flexible and easier to configure. We’ve updated the Deployment Assistant to include the following: Support for the Exchange 2013 Edge Transport server role in all on-premises and hybrid deployment scenarios Support for the new, automated process for requesting an Exchange 2013 or Exchange 2010 Hybrid Edition product key New in Exchange 2013 SP1, Edge Transport servers minimize the attack surface by handling all Internet-facing mail flow, which provides SMTP relay and smart host services for your Exchange organization, including connection filtering, attachment filtering and address rewriting. For more information, see Edge Transport Servers. Also newly released, you can now use the new product key wizard to submit your request to Microsoft Support to obtain an Exchange 2013 or Exchange 2010 product key for use in hybrid deployments. The request process is quick and easy and you’ll have your product key in minutes! You can request a Hybrid Edition product key if all the following conditions apply to you: You have an existing, non-trial, Office 365 Enterprise subscription You currently do not have a licensed Exchange 2013 or Exchange 2010 SP3 servers in your on-premises organization You will not host any on-premises mailboxes on the Exchange 2013 or Exchange 2010 SP3 server on which you apply the Hybrid Edition product key And, there’s even more on the way! We’re working hard on testing and adding new deployment scenarios to support configuring hybrid deployments with an Office 365 tenant and multi-forest on-premises Exchange organizations. We’ll start by supporting scenarios for multi-forest Exchange 2010 organizations that add Exchange 2013 SP1 servers for hybrid support, and then follow with scenarios supporting for native multi-forest Exchange 2013 and Exchange 2007 organizations. Keep checking back here for release announcements. In case you're not familiar with it, the Exchange Server Deployment Assistant is a free web-based tool that helps you deploy Exchange 2013 or Exchange 2010 in your on-premises organization, configure a hybrid deployment between your on-premises organization and Office 365, or migrate completely to Office 365. The tool asks you a small set of simple questions and then, based on your answers, creates a customized checklist with instructions to deploy or configure Exchange Server. Instead of trying to find what you need in the Exchange library, the Deployment Assistant gives you exactly the right information you need to complete your task. Supported on most major browsers, the Deployment Assistant is your one-stop shop for deploying Exchange. Do you have a deployment success story about the Deployment Assistant? Do you have suggestions on how to improve the tool? We would love your feedback and comments! Feel free to leave a comment here, or via the 'Feedback' link located in the header of every page of the Deployment Assistant. Happy deploying! The Deployment Assistant Team
How can I report an error in MS Teams documentation?
Hey all, how can I report an error that I noticed in MS teams documentation? On this site: https://learn.microsoft.com/en-us/microsoftteams/phone-reference/manage-numbers/phone-number-management-for-slovenia There is a LOA request that is named: "Letter of Authorization (LOA) for Slovania (all numbers) (v.1.0)". This is of course an error - it should say Slovenia, not Slovania. How do I report this to MSFT for checking and fixing the Learn docs? I cannot seem to edit or submit a PR for MS teams. Thanks! BR TimPortable Azure topology and documentation snapshots with OSIRIS JSON
Ciao everyone, I’m working on https://github.com/osirisjson/osiris, a vendor-neutral specification for describing infrastructure resources and their relationships as portable point-in-time snapshots. To proof that the specification could work in real-scenarios I already built an initial https://osirisjson.org/en/docs/producers/hyperscalers/microsoft-azure in Go. You run on-premise and it connects through the Azure CLI, reads Azure subscriptions and emits an OSIRIS JSON document that can be used for documentation, topology diagrams, audits, configuration drift analysis, CMDB/IPAM/DCIM workflows, or controlled AI/context workflows without giving those platforms/tools direct access to Azure. The producer currently covers several Azure areas, including networking, compute, storage, identity, databases, containers, integration, observability, backup, automation, management groups, and cross-resource dependency edges such as Private Endpoint to PaaS targets, App Service to Application Insights / Log Analytics, AKS to subnets and node pools, and backup vault relationships. It supports two output purposes: documentation: minimal high-level projection for diagrams, inventory dashboards, and architectural documentation audit: deeper projection with readable properties and extensions after sensitive-field redaction This is not intended to replace Azure tooling, Azure Resource Graph, IaC, Azure Policy, or any existing governance/control-plane workflow. OSIRIS JSON is simply a read-only external producer that generates a vendor-neutral snapshot of the observed Azure environment. I would really appreciate feedback from Azure architects, cloud engineers, and governance practitioners on the mapping model: Which Azure resources and relationships are the most important for documentation and topology generation? Are the current connection types useful for real-world architecture views? What should be prioritized in next releases? Would a documentation/audit split be useful in enterprise environments? You find the current Azure producer documentation here: https://osirisjson.org/en/docs/producers/hyperscalers/microsoft-azure I would really appreciate any feedback, suggestions, edge cases, or ideas from people who operate, document, audit, or govern Azure environments and I also welcome anyone who want to participate on development. Ciao from Italy, Tia
