Showing posts with label Microsoft 365. Show all posts
Showing posts with label Microsoft 365. Show all posts

Monday, November 25, 2024

“Book of News” for Microsoft Ignite 2024

Book of News for MS Ignite 2024 for the full set of announcements we’ve made at Microsoft Ignite 2024, and the Official Microsoft Blog  to learn more about our key announcements.

Here’s the Table of Contents:

    • 1.1. Agents 
    • 1.2. Microsoft 365 Copilot 

    • 2.1. Collaboration 
    • 2.2 Investment in AI 

    • 3.1. AI 
    • 3.2. Developer Tools 
    • 3.3. Infrastructure 
    • 3.4. Data & Analytics 
    • 3.5. Quantum 

    • 4.1. Edge 

    • 5.1. Industry 

    • 6.1. Microsoft 365 

    • 7.1. Power Platform 

    • 8.1. Security 
    • 8.2. Microsoft Purview 
    • 8.3. Security Copilot 
    • 8.4. Intune 
    • 8.5. Entra 
    • 8.6. Defender 

    • 9.1. Windows Commercial 
    • 9.2. Windows Developer 

Monday, August 22, 2022

How to filter Bing results by Date? The Date filter is missing on bing, here is a work-around

 

Intro:

On bing.com can I filter the All results by Date using the UI?

More Information:

I have used bing.com from Edge Chromium, Edge Mobile, Google Chrome, logged into MS365 and logged out and in a private window.

The result is the same: I am unable to filter search results by date using the UI, the “Any time” drop down is gone.

Question:

Is there any solution besides tweaking the query string or adding special condition to a search?

Can we get the "Any time" drop down returned to the Bing search screen for All?

I would love to use Bing but without a Date filter feature that at least mimics Duckduckgo or at best matches google there is NO way I would ever recommend Bing for the business or home.

Solution:

From below Attempted Workarounds:
1) Add ‘Narrow by Date’ query sting params to url : 
&tbs=qdr:y
with:
 6) Add narrow by date to default search engine:
{bing:baseURL}search?q=%s&tbs=qdr:y&{bing:cvid}{bing:msb}

Attempted Workarounds

Here are the options that I have currently tried , I am personally using option 1 with 6 but it works for only my general searches. When I need something narrower like “Last Month” I have to tweak the url again.

 

1) Add ‘Narrow by Date’ query sting params to url

                last day

                &tbs=qdr:d

                or year

                &tbs=qdr:y

                Only date param that seems to use DatePublished and mimics duckduckgo / google functionality

                

 

               

2 ) Add Freshness (not same as datePublished)

                freshness=week

                freshness=2021-08-23..2022-08-23

                This is useless because freshness as design "Freshness refers to the date that Bing originally discovered the webpage, not when the publisher published the webpage." per MS

               

3) Adding datePublished to search (not sure what this does, does not seem to work)

                eg: datePublished=YYYY-MM-DD

4) Adding date range to search value: (doesn’t work)

                eg  "test search" (Jan. 1 - Feb 18)

5) Some unrelated setting? (doesn’t work)

                On the Worldwide screen, select “United States English”. For their own reasons, Bing only supports search-by-date in the United States.

                https://www.oyetimes.com/lifestyle/technology/52485-how-to-enable-bing-search-by-date

 6) Add narrow by date to default search engine:

{bing:baseURL}search?q=%s&tbs=qdr:y&{bing:cvid}{bing:msb}






Using narrow by Date results

 Appendix: Compare results with and without &tbs=qdr:y

 

With Narrow by Date


 

Without narrow by date









Friday, August 19, 2022

Azure Microsoft Graph Explorer Permissions : How to resolve "Application must have one of the following scopes" Error

Symptoms: 

When using the MS Graph Explorer in Azure: 

Summary:

Resolving the error "Application must have one of the following scopes"  when accessing the GraphAPI


Detail: 

If you receive an error with the following substring part in the error message:

"Application is not authorized to perform this operation."

and/or

"Application must have one of the following scopes:"

When accessing the service url : https://graph.microsoft.com/beta/deviceManagement



An example response:

 {

    "error": {
        "code": "Forbidden",
        "message": "{\r\n  \"_version\": 3,\r\n  \"Message\": \"Application is not authorized to perform this operation. Application must have one of the following scopes: DeviceManagementConfiguration.Read.All, DeviceManagementConfiguration.ReadWrite.All - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 5c977c7f-ae03-4be0-82c2-408eafb65caf - Url: <https://fef.msub05.manage.microsoft.com/DeviceConfiguration_1911/StatelessDeviceConfigurationFEService/deviceManagement?api-version=5019-09-20>\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n  \"HttpHeaders\": \"{}\"\r\n}",
        "innerError": {
            "request-id": "5c977c7f-ae03-4be0-82c2-408eafb65caf",
            "date": "2019-11-15T18:53:00"
        }
    }
}

Resolution:

  1. Sign in to the Azure portal, go to Azure Active Directory > Enterprise Applications, and then select Graph explorer from the list of applications. For example for me : Enterprise Application is at this url 



  2. Click "Graph Explorer"

  3. Click Permissions



  4. Search for, Add and then Grant the permission that we want Graph Explorer to execute without error:



  5. With our permission added, we can now execute without error:


  6. Execute: