Edge pdf text addition = massive file size increase
As of today, when I add just a small amount of text (20-30 characters) to a pdf and save, the file size increases from 66KB to 55,000KB ... never happened before. I've reported to Microsoft but they have no solutions. Any ideas to get around? Saving as a separate file has same result. ThanksSharing: PDF readers that support Purview labels
As I was researching on Adobe Acrobat reader and Sensitivity labels, I decided to check if the common alternative PDF readers out there are able to support Purview MIP Sensitivity labels. There is already a published documentation on this for SharePoint-Compatible PDF readers that supports Microsoft IRM: https://learn.microsoft.com/en-us/purview/sp-compatible-pdf-readers-for-irm (last updated Nov-2023) but I wanted to see if these same PDF readers supports the ability for end-users to use/ select labels similar to that of Adobe Acrobat As of 11-June-2025; atleast one of them clearly do: Nitro PDF: Yes. Documentation shows that users can see and use the sensitivity labels. PDF -X.change Editor: Yes. Documentation show that users can see and use the sensitivity labels. (check the official website, I can't hyperlink it because the site is blocked. FOX PDF editor: No. Documentation only states RMS and not clear if it show Purview labels. This is for F.O.X.I.T editor (spelled without the ".") but for some reason there is a community ban on that word and it won't allow me to post the full name PDFescape: No. Sumatra PDF: No Okular: No If there are other PDF readers that I've missed, I encourage you list it down in the comment below. Would love to grow this list.Access fixes released in Version 2603 (Build 19822.20114)
Here's a summary of bug fixes in the latest version of Access: Bug Name Issue Fixed Edge Browser Control didn't navigate from code when inside a tab control When the Edge Browser control was hosted in a tab control, calls to the Navigate method from VBA succeeded, but the control didn’t refresh to show the new page. Switching tabs forced the refresh. The control now refreshes automatically after navigation, even when it’s hosted in a tab control. Some Unicode characters displayed incorrectly in Quick Import Certain extended Unicode characters were displayed as squares when importing data using Quick Import. These characters are now displayed correctly. Modern Chart titles truncated in Print Preview When viewing a report containing Modern Charts in Print Preview, chart titles might be truncated. Chart titles now render correctly in Print Preview. Some Unicode characters displayed incorrectly in exported object names When exporting an object whose name contained certain extended Unicode characters, the sheet name in the exported file displayed the characters incorrectly. These characters are now preserved correctly during export. Some Unicode characters displayed incorrectly in error messages for long object names When renaming a database object to a name that was too long, the error message displayed certain extended Unicode characters incorrectly. These characters now display correctly in error messages. Standard colors in Access didn't match other Office apps The standard color palette in Access used different color values than other Office applications like Word and Excel. For example, the standard red in Access was #ED1C24 instead of the updated Office standard red #EE0000. The color palette has been updated to match the rest of Office. Field.Properties("Precision") and Properties("Scale") on a query column caused the query to execute Accessing the Precision or Scale properties of a field in a query's Fields collection caused the query to execute. This was a regression that broke add-ins and code that enumerate field properties, since query execution can be expensive and have side effects. These properties are now returned without executing the query. Toggle filter button in status bar didn't work when no records were displayed When a form filter resulted in no matching records, clicking the Toggle Filter button in the status bar to remove the filter had no effect. The button now properly removes the filter even when the filtered result set is empty. PDF files with capitalized extension didn't render in Edge Browser Control When navigating to a PDF file using the Edge Browser control, if the file extension was capitalized (e.g., ".PDF" instead of ".pdf"), the file contents were rendered as raw text instead of as a formatted PDF document. The extension comparison is now case-insensitive. Monaco SQL editor inserted blank lines in multi-line comments When switching between Design View and SQL View, the Monaco SQL editor inserted blank lines between each line inside /* multi-line comment */ blocks. This affected both local and passthrough queries. The editor now preserves the original comment formatting. Please continue to let us know if this is helpful and share any feedback you have.
Feature Request: PDF Layer Support in the new Adobe PDF Engine for Edge
Beschreibung: Mit der Umstellung des integrierten PDF‑Viewers in Microsoft Edge auf die Adobe Acrobat PDF‑Engine (Rollout ab 2023, vollständige Ablösung des Legacy‑Engines bis Juni 2026) ist es entscheidend, dass wichtige Profi‑Funktionen nicht verloren gehen. Ein zentraler Wunsch vieler Anwender ist die vollständige Unterstützung von PDF‑Layern. Gerade in technischen Bereichen – etwa bei CAD‑Zeichnungen, Bauplänen oder Schaltbildern – sind Layer unverzichtbar, um Inhalte gezielt ein‑ oder auszublenden und komplexe Dokumente verständlich darzustellen. Wir bitten darum, sicherzustellen, dass die neue Adobe‑Integration in Edge auch diese Layer‑Funktionalität nativ unterstützt. Ohne diese Funktion bleibt Edge für professionelle PDF‑Workflows eingeschränkt und zwingt Nutzer weiterhin zu Dritt‑Viewern. Use‑Case‑Beispiele: Elektrotechnik: Kabelpläne mit Layern für Signal‑, Strom‑ und Steuerleitungen Architektur: Baupläne mit Layern für unterschiedliche Gewerke (Elektro, Sanitär, Statik) Dokumentation: Technische Handbücher mit optionalen Layern für Detailansichten Eine native Layer‑Unterstützung würde die neue Adobe‑Engine in Edge deutlich aufwerten und den Einsatz für Fachanwender erheblich verbessern. gb-EN Description: With Microsoft Edge transitioning its built‑in PDF viewer to the Adobe Acrobat PDF engine (rollout starting in 2023, legacy engine removed by June 2026), it is crucial to ensure that key professional features are not overlooked. One of the most requested capabilities is full support for PDF layers. In technical fields – such as CAD drawings, construction plans, or electrical schematics – layers are essential to selectively show or hide content and make complex documents easier to understand. We kindly ask that the new Adobe integration in Edge natively supports PDF layers. Without this functionality, Edge remains limited for professional PDF workflows and forces users to rely on third‑party viewers. Use‑Case Examples: Electrical engineering: cable diagrams with separate layers for signal, power, and control lines Architecture: construction plans with layers for different trades (electrical, plumbing, structural) Documentation: technical manuals with optional detail layers Native layer support would significantly enhance the Adobe PDF engine in Edge and make it far more valuable for professional users.
Microsoft Forms integration in Teams has a bug/malfunction
Microsoft Teams has the option to integrate Microsoft Forms as a tab to a Teams Channel: When in Microsoft Forms 'Allow receipt of responses after submission' is ticked, this should enable the respondent to save the submission as a PDF (or print it): This button (shown below) however allows the user to save as PDF in Edge, but is malfunctioning when clicked upon in Microsoft Teams: Clicking this button in Microsoft Teams environment does open up a window, but it only allows the user to print the form. Saving/downloading the submisson as PDF is not working in Microsoft Teams. In the ideal situation the Save as PDF should be the dominant function, and the print option should be option.
PDF
Hallo Wenn man auf Teams eine Tabelle anlegt und diese anschließend als PDF-Dokument haben möchte, kann man diese nicht direkt über Teams in ein PDF-Dokuemnt umwandeln? Bei mir funktioniert es nur, wenn ich die Tabelle per Excel / SharePoint öffne und dann als pdf umwandel? Danke für eure Hilfe"Solutions - Is there a way to Scan & Annotate PDF Directly to Teams?
Hey Looking for a solution to our problem. We have Teams/365 installed across our network - and really loving the collaborative work. The issue we have is - our Warehouse Team is located on the other side of the building. They receive deliveries, with delivery notes, however, they delivery notes need to be checked off and annotated by the operations director in the head office. This is normally done by a warehouseman coming to head office, the operations director looking through the delivery note and handwriting all over them to identify and allocate the different items on the note. The warehouseman, then goes back to warehouse and hands it to the warehouse Manager to assign where the deliveries go or what needs to be done with them. What i was wondering is what would be the best solution for this, using Teams? I was thinking of getting a little mini scanner, for the warehouse manager, to be able to scan and then the operations director could annotate it from his desktop and the Warehouse manager would be able to see it from teams. and really I was wondering: 1) Can you scan directly into a Teams Conversation/Task/Teams? 2) Is there a method to then annotate the PDF that had been scanned? 3) Will it store it (not essential, but would be good) Alternatively, i am more than happy to go with any other solution if anyone has any cool ideas!? Many thanks for your time!
File association getting reset for PDF
Pdf files association getting reset to Chrome and edge randomly daily after changing Adobe Acrobat 2017 as default. Effected machines are windows 10 enterprise 20H1 and 20H2 We updated some machines to 20h2 and got same behaviour. Approx impact 300 users at client side. GPO and GPP are not helpful. We doubt it's bug related to file association. Anyone else facing same issue ?
