Add SOCKS5 (+ Authentication) support to Edge insider browser
Hi, Please consider adding SOCKS5 proxy support and Authentication (username and password) to the new Edge browser. currently only Firefox has that capability (without Auth). Microsoft Edge insider is using the same networking settings as google chrome which is not ideal and heavily relies on extensions and 3rd party programs. please create a separate proxy settings page that only effects Edge browser (like Firefox) and Not the whole Windows OS, and add SOCKS5 support to it. ThanksTHEMES - Now available in Edge Addons store
https://microsoftedge.microsoft.com/addons/microsoft-edge-themes Personalize Edge with themes that change the look and feel of your browser and the new tab page to create beautiful and immersive visual experiences. Apply different themes to each profile to help you easily separate home, school, or work. We'll be adding more themes soon, so stay tuned! The category is awesome, contains some game-specific themes too! so which one are you going to use?
Script to view users phone numbers or extensions in tenant
Hello, We are moving from Skype Online to Teams and we are assigning extensions to our users. Does anyone know of a simple script that can output "Username" and "Teams Phone Number or Teams Extension" I've tried a few scripts but nothing seems to give me the information I need. Thanks!Windows Admin Center needs a Group Policy Extension for GPMC
That's one of the important things that is missing in WAC 1907. even if not as part of the main features, make it available as an extension to optionally install it whoever needs it. Then, Microsoft can expect people to move from RSAT to the new WAC.Kaspersky Protection extension still is Not working with Edge Stable/Beta
Kaspersky Protection gets automatically installed by installing Kaspersky Internet security 2020 which is the best AV out there. yet its extension is not compatible even with Edge insider (Release candidate) or Stable enterprise, both version 79. and they are going to be released to public in less than 15 days. Edge Version 79.0.309.56 (Official build) (64-bit) The fact is, this extension works perfectly on Google chrome 79 (the same version as Edge) Kaspersky Protection extension is as good as ublock origin. it blocks all the malware, adware, cryptominers, YouTube's annoying ads that pop up time to time etc etc.
LineURI with Same Phone Number and Different Extension
I have a department that wants all of their outgoing calls to go from one number. I have a set of test phones which I changed to do this process, but I wanted to make sure I am not going to break anything or cause issues at a later time. What I did was set the Line URI to be in the following format: tel:+1######3537;ext=3524 Where the tel:+1######3537 remains the same for each of the numbers, but ;ext=3524 is whatever number that phone is logged on as. It appears to work as I can still call the 3524 in this case and it rings to the correct phone or vice versa. If I call outside of our campus, caller ID displays as ###-###-3537 which is correct. Again, I want to make sure I am not causing any new issues or issues down the road. I know that the ext=#### is simply to allow us to be able to log on easily to a phone in our case using PIN. Does doing this set up cause any issues or are others doing this to control how caller ID goes out for some areas? If this works, I can see using this similar set up for department chairs or others that do not want to display their real number. For this set up, I did not want to create private numbers which we have done, but if the above process works, then I would like to set this up. We are a hybrid setup. Let me know if you there are any questions. Curious if this is going to cause me any issues now or in the future. Thank you! JohnNew Feature: CORS for extension content scripts | Manifest V3 next phase
It's behind a flag: edge://flags/#cors-for-content-scripts CORS for content scripts Prevent content scripts of Extensions from bypassing CORS. – Mac, Windows #cors-for-content-scripts Microsoft Edge Version 83.0.477.0 (Official build) canary (64-bit) Overview When web pages request cross-origin data with fetch or XHR APIs, the response is denied unless CORS headers allow it. In contrast, extension content scripts have traditionally been able to fetch cross-origin data from any origins listed in their extension's permissions, regardless of the origin that the content script is running within. As part of a broader Extension Manifest V3 effort to improve extension security, privacy, and performance, these cross-origin requests in content scripts will soon be disallowed. Instead, content scripts will be subject to the same request rules as the page they are running within. Extension pages, such as background pages, popups, or options pages, are unaffected by this change and will continue to be allowed to bypass CORS for cross-origin requests as they do today. https://www.chromium.org/Home/chromium-security/extension-content-script-fetches
